From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: 27995@debbugs.gnu.org
Subject: bug#27995: view-lossage should show the contents of prompts
Date: Mon, 07 Aug 2017 08:49:39 +0800 [thread overview]
Message-ID: <87tw1kkxr0.fsf@jidanni.org> (raw)
C-h l runs the command view-lossage.
It is great, however an improvement would be to show what the user was
prompted with.
Why? Because hitting RET is equivalent to the user typing what he was
prompted with, however the latter is never recorded.
C-x 4 b [switch-to-buffer-other-window] #prompted with mno321
<return> [minibuffer-complete-and-exit]
C-x k [kill-buffer] #prompted with xyz123
<return> [minibuffer-complete-and-exit]
Indeed even open-dribble-file doesn't capture the prompts, nor does
C-h e which runs the command view-echo-area-messages.
next reply other threads:[~2017-08-07 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 0:49 積丹尼 Dan Jacobson [this message]
2019-07-15 17:58 ` bug#27995: view-lossage should show the contents of prompts Lars Ingebrigtsen
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=87tw1kkxr0.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=27995@debbugs.gnu.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).