From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 61440@debbugs.gnu.org
Subject: bug#61440: 27.2; Be able to have `view-lossage' report only on the current buffer
Date: Sun, 12 Feb 2023 08:09:37 +0200 [thread overview]
Message-ID: <83h6vrifdq.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488773EBC91DC8A4ADE166EF3DF9@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Sat, 11 Feb 2023 21:59:09 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> Date: Sat, 11 Feb 2023 21:59:09 +0000
>
> Be able (e.g. with a prefix arg) to have `C-h l' show only the recent
> commands used in the current buffer. The max number should be the same
> as if listing the commands used in all buffers. IOW, it shouldn't just be a
> filtering of what `C-h l' without a prefix arg would give you (i.e., limited
> to the max number).
>
> It would be good to also extend `recent-keys' to accept an additional
> optional arg, to have it return only events in the current buffer.
How do you define "commands used in the current buffer"?
. are commands in the minibuffer when Emacs prompts considered to be
"used in the current buffer"?
. are commands invoked from the minibuffer via M-x considered to be
"used in the current buffer"?
. what about commands that switch to temporary buffers and enter
recursive edit there?
. what about commands that switch to another buffer in the middle of
typing a key sequence?
. etc. etc.
IOW, I don't understand how this hypothetical feature could work in
practice, let alone how to document what exactly it produces. Emacs
commands are by their very nature "global", unrelated to a buffer.
next prev parent reply other threads:[~2023-02-12 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 21:59 bug#61440: 27.2; Be able to have `view-lossage' report only on the current buffer Drew Adams
2023-02-12 6:09 ` Eli Zaretskii [this message]
2023-02-12 15:43 ` Drew Adams
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=83h6vrifdq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61440@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).