From: Psionic K <psionik@positron.solutions>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Psionic K <psionik@positron.solutions>, emacs-devel@gnu.org
Subject: Re: Proposing elisp-eval-target for eval-last-sexp and related commands
Date: Wed, 18 Aug 2021 13:19:42 +0800 [thread overview]
Message-ID: <CADQMGAQoS6hPULO=cY8NViZycEKYu=rQJzw6KNarKp2v+ODB8g@mail.gmail.com> (raw)
In-Reply-To: <jwv4kbovt7s.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
Indeed ielm is my workflow for this use case. When I shared a shortcut on
Reddit for the `ielm-change-working-buffer` solution, it was obvious that
many users have a strong preference for working in an elisp major mode
buffer. I can't provide a shortcut however because the `eval-last-sexp`
style functions don't have any `working-buffer` concept like the ielm
implementation. The change I'm proposing will allow the extremely low
friction of the ielm solution but with the freedom of an elisp major mode
buffer.
On Wed, Aug 18, 2021 at 2:11 AM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> Psionic K [2021-08-18 00:11:01] wrote:
> > Proposing to patch the eslip module so that if a buffer-local
> > `elisp-eval-target` has been set, `eval-last-sexp` and similar commands
> > will execute lisp in the context of another buffer.
> >
> > The use case is when developing elisp to operate on non-elisp buffers,
> > interacting with functionality for other languages such as when using
> LSP.
>
> `M-x ielm` lets you do just that.
>
> Having a dedicated buffer also lets it print the result more comfortably
> and show the "target buffer" in the mode line.
>
>
> Stefan
>
>
--
Psionic K <psionik@positron.solutions>
Software Engineer
*Positron Solutions <https://positron.solutions>*
[-- Attachment #2: Type: text/html, Size: 2507 bytes --]
next prev parent reply other threads:[~2021-08-18 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 16:11 Proposing elisp-eval-target for eval-last-sexp and related commands Psionic K
2021-08-17 17:30 ` Eduardo Ochs
2021-08-18 5:22 ` Psionic K
2021-08-17 18:10 ` Stefan Monnier
2021-08-18 5:19 ` Psionic K [this message]
2021-08-21 14:37 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADQMGAQoS6hPULO=cY8NViZycEKYu=rQJzw6KNarKp2v+ODB8g@mail.gmail.com' \
--to=psionik@positron.solutions \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).