GNU bug report logs - #60381
[PATCH] Preserve Window Position with Proced

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Laurence Warne <laurencewarne <at> gmail.com>
Cc: 60381 <at> debbugs.gnu.org
Subject: Re: bug#60381: [PATCH] Preserve Window Position with Proced
Date: Thu, 29 Dec 2022 16:09:30 +0200

> From: Laurence Warne <laurencewarne <at> gmail.com>
> Date: Thu, 29 Dec 2022 12:52:20 +0000
> Cc: 60381 <at> debbugs.gnu.org
> 
> before update: window point: 20235, buffer point: 20235
> after goto-char min: window point: 20235, buffer point: 1
> before erase buffer: window point: 20235, buffer point: 1
> after erase buffer: window point: 1, buffer point: 1
> after update: window point: 1, buffer point: 20235
> 
> So my understanding is since the selected window does not display a proced buffer, the window point is not
> updated in line with the buffer point, but the erase-buffer call sets the window point to start of the buffer, and
> so this is not updated in line with the buffer point in the subsequent insertion of processes.

Why cannot proced update point when the window is not the selected
one?

> The last case (the second issue) where no window shows a proced buffer is similar to the previous, but
> erase buffer instead appears to set pos for the proced buffer's value in (window-prev-buffers) if it's the case
> a window has shown a proced buffer previously.

Same question here.

And I don't think I understand how the above explains why searching
for the same process also fails.  That should be independent of
whether the buffer is displayed in the selected window or in any
window.

Previous Next

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