From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 14676@debbugs.gnu.org
Subject: bug#14676: 24.3.50; winner doesn't immediately notice windows created by server
Date: Wed, 16 Sep 2020 23:19:28 -0400 [thread overview]
Message-ID: <jwvk0wtnlio.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87a6xpffri.fsf@web.de> (Michael Heerdegen's message of "Thu, 17 Sep 2020 01:44:49 +0200")
>> Or did the problem fix itself through other means over the years?
> No, it didn't.
> The "patch" is just the change Stefan suggested, done in a more or less
> random way AFAIR, since I don't know server.el, too. I would still give
> it a try. But AFAIU the change I had posted and you quoted doesn't
> fulfill what the current code says, namely that `post-command-hook'
> should be run in each buffer individually. Maybe that's the reason why
> Stefan had ignored it ;-)
BTW, runnning `post-command-hook` in there is arguably wrong (we didn't
technically run a command, or at least we didn't go through the usual
"protocol" of running a command, so some `post-command-hook` functions
may misbehave, e.g. because of interaction with things like
`this-command` or `last-command`).
Maybe the right way to fix this is to try and make `server.el` simulate
more carefully a command-loop running a command. Or even *really* make
it run a command. E.g. instead of having `server.el` immediately
run within the process filter the code requested by the client, it could
just push some ad-hoc event onto `unread-command-events` which is then
bound to a command.
Stefan
prev parent reply other threads:[~2020-09-17 3:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 18:09 bug#14676: 24.3.50; winner doesn't immediately notice windows created by server Michael Heerdegen
2013-06-20 20:31 ` Stefan Monnier
2013-06-20 21:00 ` Stefan Monnier
2013-06-20 21:54 ` Michael Heerdegen
2013-06-21 14:38 ` Stefan Monnier
2013-06-22 22:44 ` Michael Heerdegen
2020-09-09 13:41 ` Lars Ingebrigtsen
2020-09-16 23:44 ` Michael Heerdegen
2020-09-17 3:19 ` Stefan Monnier [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=jwvk0wtnlio.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=14676@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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).