GNU bug report logs - #67993
Selecting buffer automatically

Previous Next

Full log

Message #51 received at 67993 <at> debbugs.gnu.org (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: Juri Linkov <juri <at> linkov.net>
Cc: 67993 <at> debbugs.gnu.org
Subject: Re: bug#67993: Selecting buffer automatically
Date: Mon, 15 Jan 2024 11:23:14 +0100

> However, the name 'select-window' would be too confusing for users
> because based on such name they will expect that it will select
> the window immediately after it's displayed.
>
> Therefore I propose to rename it to the less ambiguous name
> 'post-command-select-window'.  Of course it should be documented in
> any case, but this will help the users who never read the documentation.

That's better.

> Ok, here is a complete patch with the documentation:

+ `post-command-select-window' -- A non-nil value means that after the
+    current command is executed and the hook `post-command-hook' is called,
+    the window displayed by this function will be selected.  A nil value
+    means that if functions like `pop-to-buffer' selected another window,
+    at the end of this command that window will be deselected, and the
+    window that was selected before calling this function will remain
+    selected.

I'd say "will be usually selected" and "will be usually deselected".
For example, (post-command-select-window . nil) will effectively select
the window that was selected before 'display-buffer' was called,
regardless of which other window were selected after the
'display-buffer'.  Think of

(progn
  (select-window x)
  (pop-to-buffer ... '(post-command-select-window . nil))
  (select-window y))

which will select x overriding the call to select y.  Or think of two
'display-buffer' calls within one and the same command.

martin

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.