From: Ami Fischman <ami@fischman.org>
To: martin rudalics <rudalics@gmx.at>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: display-buffer vs. current-buffer vs. post-command-hook
Date: Tue, 04 Oct 2016 15:45:00 +0000 [thread overview]
Message-ID: <CAGKqTXUSk+RjdY0x5s=+n6gaKdLM2WRj6N2Oxw+yB0+FYBDSqA@mail.gmail.com> (raw)
In-Reply-To: <57F3C212.3020401@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]
>
> ‘describe-key’ is based on ‘with-temp-buffer-window’ which tries very
> hard to restore the current buffer after doing its work. So what you
> see here is not a stale value but one that has been correctly preserved.
>
I'm sorry but I don't understand your statement. Should there not be an
expectation that (current-buffer)'s return value does not change between
the second and third call in my original snippet?
Put another way, under what circumstances should one expect
current-buffer's return value to be stable in user-written elisp?
Put a third way, what about describe-keys documentation should lead an
elisp author to understand that current-buffer will not reflect its effect
until after a [run-at-time 0]?
(sorry for the barrage of questions; I feel there's a fundamental something
I'm missing in play here and trying to see if you know what it is :))
Please tell us what you want to accomplish. Then we might be able to
> tell you how to do that.
My original goal was to resolve a bug in the interaction between two add-on
libraries (see the link in my original email). That bug has been fixed by
replacing the uses of current-buffer with window-buffer so my original goal
is now moot. Now my goal is to understand the intended semantics of
interaction between current-buffer and describe-key (and its impl).
Cheers,
-a
[-- Attachment #2: Type: text/html, Size: 1868 bytes --]
next prev parent reply other threads:[~2016-10-04 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 9:28 display-buffer vs. current-buffer vs. post-command-hook Ami Fischman
2016-10-04 12:00 ` Stefan Monnier
2016-10-04 14:52 ` martin rudalics
2016-10-04 15:45 ` Ami Fischman [this message]
2016-10-04 15:49 ` Ami Fischman
2016-10-04 16:07 ` martin rudalics
2016-10-04 20:03 ` Ami Fischman
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='CAGKqTXUSk+RjdY0x5s=+n6gaKdLM2WRj6N2Oxw+yB0+FYBDSqA@mail.gmail.com' \
--to=ami@fischman.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).