From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 15811@debbugs.gnu.org
Subject: bug#15811: 24.3.50; enhancement request: provide history for *Pp Eval Output*
Date: Fri, 29 Apr 2016 10:36:55 -0700 (PDT) [thread overview]
Message-ID: <c88c6911-1baa-49c5-9eb5-b23d6fe7c1ef@default> (raw)
In-Reply-To: <87inz07bn2.fsf@gnus.org>
> > Consider providing a navigable history for buffer *Pp Eval Output*.
> > This would be similar to `l' and `r' in *Info* or the [back] and
> > [forward] links in *Help*. But instead of adding links to the buffer,
> > use keys or menu items.
> >
> > Currently there is not even any undo in *Pp Eval Output*. It can be
> > useful to revisit previous evaluation results.
>
> If we're storing the expressions in the history and redoing them, then
> that sounds potentially dangerous. (There may be something destructive
> going on.) If we're saving the buffer contents, then that sounds
> ... unusual.
It's no different from what we do with `*Help*', except that
yes, I meant saving the buffers (output), not automatically
reevaluating the sexps. As I said: "useful to revisit previous
evaluation results".
Your criticism in that case is that this would be "unusual"?
Not for someone who uses *Pp Eval Output* a lot. This is
similar to requests for saving *grep* buffers etc.
The other possibility to consider is simply providing undo,
so you can go backward to previous results (and forward again).
That would less handy than separate buffers with navigation,
but it would be better than nothing.
> So I don't think this sounds like a very useful feature. Closing.
prev parent reply other threads:[~2016-04-29 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 16:23 bug#15811: 24.3.50; enhancement request: provide history for *Pp Eval Output* Drew Adams
2013-11-05 20:24 ` Glenn Morris
2016-04-29 14:06 ` Lars Ingebrigtsen
2016-04-29 17:36 ` Drew Adams [this message]
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=c88c6911-1baa-49c5-9eb5-b23d6fe7c1ef@default \
--to=drew.adams@oracle.com \
--cc=15811@debbugs.gnu.org \
--cc=larsi@gnus.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).