From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: "52023@debbugs.gnu.org" <52023@debbugs.gnu.org>
Subject: bug#52023: [External] : Re: bug#52023: 27.2; Enhancement: `this-command-invocation-(buffer|window)'
Date: Mon, 22 Nov 2021 10:06:10 +0200 [thread overview]
Message-ID: <86pmqstxxs.fsf@mail.linkov.net> (raw)
In-Reply-To: <SJ0PR10MB54884F949A4ACD455C8D4031F39E9@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Sun, 21 Nov 2021 21:36:49 +0000")
>> Maybe these functions give what you need?
>>
>> (old-selected-window)
>> (window-buffer (old-selected-window))
>...
> As for the second sexp you show: the buffer
> that's current when a command is invoked
> need not be displayed in any window.
It seems there is no such thing as `old-current-buffer'
like there is `current-minibuffer-command'.
> As for the first (function `old-*'), the
> doc says ~ it's the window selected at the
> time of (before? after?) the last window
> change.
>
> It's not clear to me whether that's the
> `selected-window' when this-command was
> invoked. Is it? always?
I don't know what `old-selected-window' returns when
more window changes were performed by the same command.
But in any case you can use `pre-command-hook' to store
the original buffer and window.
next prev parent reply other threads:[~2021-11-22 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 18:11 bug#52023: 27.2; Enhancement: `this-command-invocation-(buffer|window)' Drew Adams
2021-11-21 19:19 ` Juri Linkov
2021-11-21 21:36 ` bug#52023: [External] : " Drew Adams
2021-11-22 8:06 ` Juri Linkov [this message]
2021-11-22 15:17 ` Drew Adams
2021-11-22 17:46 ` Juri Linkov
2021-11-22 20:00 ` Drew Adams
2022-09-24 13:31 ` 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=86pmqstxxs.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=52023@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).