GNU bug report logs - #50256
thing-at-mouse

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 50256 <at> debbugs.gnu.org, larsi <at> gnus.org, juri <at> linkov.net
Subject: Re: bug#50256: thing-at-mouse
Date: Thu, 02 Sep 2021 12:02:50 +0300

> Cc: juri <at> linkov.net, 50256 <at> debbugs.gnu.org
> From: martin rudalics <rudalics <at> gmx.at>
> Date: Thu, 2 Sep 2021 10:54:44 +0200
> 
>  > If we want to support the current documentation to the letter, the
>  > only way of doing that I know of is to force WINDOW to display the
>  > current buffer, at least internally, i.e. to switch to the WINDOW's
>  > buffer for the duration of pos-visible-in-window-p.  If that leaves
>  > everyone happy, it could be done relatively easily, but then I wonder
>  > why does the code in question with-current-buffer, and what would
>  > break when pos-visible-in-window-p internally switches back to the
>  > buffer shown in WINDOW?
> 
> pos_visible_p already does
> 
>    if (XBUFFER (w->contents) != current_buffer)
>      {
>        old_buffer = current_buffer;
>        set_buffer_internal_1 (XBUFFER (w->contents));
>      }

I'm asking if this is the desired behavior, when Lisp runs this inside
with-current-buffer?

Previous Next

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