GNU bug report logs - #68235
29.1.90; Switching tabs stops following process output in selected window

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juri Linkov <juri <at> linkov.net>
Cc: rudalics <at> gmx.at, 68235 <at> debbugs.gnu.org, daniel.c.mccarthy <at> gmail.com
Subject: Re: bug#68235: 29.1.90; Switching tabs stops following process
 output in selected window
Date: Thu, 04 Jan 2024 19:48:28 +0200

> From: Juri Linkov <juri <at> linkov.net>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  Dan McCarthy
>  <daniel.c.mccarthy <at> gmail.com>,  68235 <at> debbugs.gnu.org
> Date: Thu, 04 Jan 2024 19:07:39 +0200
> 
> Everything works nicely, and point follows the output,
> when this code is removed from 'tab-bar-select-tab':
> 
>   ;; set-window-configuration does not restore the value of
>   ;; point in the current buffer, so restore it separately.
>   (when (and (markerp wc-point)
>              (marker-buffer wc-point)
>              ;; FIXME: After dired-revert, marker relocates to 1.
>              ;; window-configuration restores point to global point
>              ;; in this dired buffer, not to its window point,
>              ;; but this is slightly better than 1.
>              ;; Maybe better to save dired-filename in each window?
>              (not (eq 1 (marker-position wc-point))))
>     (goto-char wc-point))

Maybe we should make exceptions in buffers like *completions*?

In general, restoring point is a good idea.

> The problem is that I still can't figure out in what cases point should be
> restored manually.

When the buffer was shown in another window, I think.  Martin might
have a definite answer.

Previous Next

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