From: Juri Linkov <juri@jurta.org>
To: Eli Barzilay <eli@barzilay.org>
Cc: bug-gnu-emacs@gnu.org, 4118@emacsbugs.donarmstrong.com
Subject: bug#4118: 23.1; eval-last-sexp-print-value is inconvenient
Date: Wed, 12 Aug 2009 23:57:59 +0300 [thread overview]
Message-ID: <87ocqkfxa5.fsf@mail.jurta.org> (raw)
In-Reply-To: <19073.20002.692770.552510@winooski.ccs.neu.edu> (Eli Barzilay's message of "Tue, 11 Aug 2009 06:55:30 -0400")
> `eval-last-sexp' is often useful with a prefix argument inside a
> buffer for all kinds of programmatic uses (for example, make a
> keyboard macro that massages some text into an S-expression, then
> use it to plant the result in the buffer). This uses
> `eval-last-sexp-print-value', which will "helpfully" insert other
> junk into the buffer (the hex and the octal representations of the
> number).
But it inserts other representations only when you type `C-x C-e' twice.
Do you mean you don't want this after the second `C-x C-e' key press?
> This is cute to have on the echo area, but annoying for
> such use in macros. It would be better to disable this extra output
> in the case of non-echo-area output.
Sometimes I use `C-x C-e C-u C-x C-e' to insert other representations
to the current buffer to be able to copy their values as text. Of course,
it's possible to copy them from the *Messages* buffer, but this is
less convenient.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-08-12 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 10:55 bug#4118: 23.1; eval-last-sexp-print-value is inconvenient Eli Barzilay
2009-08-12 20:57 ` Juri Linkov [this message]
2009-08-13 1:18 ` Eli Barzilay
2009-08-13 23:33 ` Juri Linkov
2009-08-14 1:25 ` Eli Barzilay
2009-08-14 22:54 ` Juri Linkov
2009-08-15 1:38 ` Eli Barzilay
2009-08-15 23:16 ` Juri Linkov
2009-08-16 0:00 ` Eli Barzilay
2009-08-17 0:52 ` Juri Linkov
2009-08-17 3:18 ` Eli Barzilay
2016-06-15 0:35 ` Noam Postavsky
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=87ocqkfxa5.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=4118@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=eli@barzilay.org \
/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).