buffer-env VS verb

buffer-env: A pure-Elisp version of the direnv utility. Useful to make Emacs aware of Python virtualenvs (which, judging by the questions posted here, is unfortunately still a complication for a lot of people). Similar to (and inspired by) envrc, but doesn't require the direnv program.

If you are interested in a “direnv but in Elisp”, you may want to check out this package: https://github.com/astoff/buffer-env.

buffer-env or envrc for virtual environment integration.

plz-see: Interactive HTTP client, similar to restclient and verb, but using Elisp instead of a special text-based syntax.

Ah, btw. I just realized, verb's verb-send-request-on-point doesn't always properly work with source blocks. So I pushed a fix, PR is here.

have you checked this https://github.com/federicotdn/verb . Its emacs package and i am able to write and test api's with text files.

Not as usable for testing, but verb.el[1] is a great tool for doing something very similar in org-mode

[1] https://github.com/federicotdn/verb

I've been a long time user of the org-mode code blocks feature—storing runnable code block inline in the document. Something I've recently started using is verb to include HTTP requests in my documents when I'm testing out web APIs.

Looks also interesting, but it doesn't fit my use cases: I need custom functions to grab values/data from other sources (e.g. pocket-reader.el).restclient` is more about having pre-defined HTTP requests (path, headers, payload etc.) in a buffer and a major mode for executing the requests. Pretty much the same what verb offers.

There is also verb.el.