From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50256@debbugs.gnu.org, larsi@gnus.org, juri@linkov.net
Subject: bug#50256: thing-at-mouse
Date: Thu, 2 Sep 2021 16:43:02 +0200 [thread overview]
Message-ID: <d650967e-235b-c40e-810f-6aed40f57d46@gmx.at> (raw)
In-Reply-To: <83k0jznms2.fsf@gnu.org>
>> >> 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?
>>
>> It is the _necessary_ behavior when WINDOW is not the selected window
>> and its buffer is not current.
>
> But in the case in point, WINDOWS _was_ the selected window. That's
> why pos-visible-in-window-p used PT. Which is what you said was the
> bug. Or am I missing something?
No. The above was meant in response to your earlier:
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.
I mean that we needn't do that because pos_visible_p already does it.
So I'd just propose to do the trivial (line numbers are not trunk's);
diff --git a/src/window.c b/src/window.c
index cb8fe5fcdb..bfbed01749 100644
--- a/src/window.c
+++ b/src/window.c
@@ -2199,8 +2199,6 @@ DEFUN ("pos-visible-in-window-p", Fpos_visible_in_window_p,
posint = -1;
else if (!NILP (pos))
posint = fix_position (pos);
- else if (w == XWINDOW (selected_window))
- posint = PT;
else
posint = marker_position (w->pointm);
martin
next prev parent reply other threads:[~2021-09-02 14:43 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 17:21 bug#50256: thing-at-mouse Juri Linkov
2021-08-29 20:03 ` Lars Ingebrigtsen
2021-08-30 7:20 ` Juri Linkov
2021-08-31 0:04 ` Lars Ingebrigtsen
2021-08-31 6:49 ` Juri Linkov
2021-08-31 17:52 ` Juri Linkov
2021-09-01 7:17 ` Juri Linkov
2021-09-01 7:43 ` Lars Ingebrigtsen
2021-09-01 9:18 ` martin rudalics
2021-09-01 12:16 ` Eli Zaretskii
2021-09-01 14:25 ` martin rudalics
2021-09-01 15:59 ` Eli Zaretskii
2021-09-01 16:21 ` martin rudalics
2021-09-01 17:54 ` Eli Zaretskii
2021-09-01 17:59 ` Juri Linkov
2021-09-01 19:23 ` Eli Zaretskii
2021-09-02 6:16 ` Juri Linkov
2021-09-02 7:21 ` Eli Zaretskii
2021-09-02 7:23 ` Lars Ingebrigtsen
2021-09-02 7:34 ` Eli Zaretskii
2021-09-02 6:48 ` martin rudalics
2021-09-02 7:30 ` Eli Zaretskii
2021-09-02 7:32 ` Lars Ingebrigtsen
2021-09-02 7:46 ` Eli Zaretskii
2021-09-02 8:54 ` martin rudalics
2021-09-02 9:02 ` Eli Zaretskii
2021-09-02 12:42 ` martin rudalics
2021-09-02 13:13 ` Eli Zaretskii
2021-09-02 14:43 ` martin rudalics [this message]
2021-09-02 15:58 ` Juri Linkov
2021-09-02 18:28 ` Juri Linkov
2021-09-02 18:41 ` Eli Zaretskii
2021-09-03 7:40 ` martin rudalics
2021-09-03 11:06 ` Eli Zaretskii
2021-09-04 7:34 ` martin rudalics
2021-09-04 8:02 ` Eli Zaretskii
2021-09-04 11:10 ` martin rudalics
2021-09-04 11:35 ` Eli Zaretskii
2021-09-04 18:58 ` Juri Linkov
2021-09-05 7:50 ` martin rudalics
2021-09-05 7:50 ` martin rudalics
2021-09-05 9:24 ` Eli Zaretskii
2021-09-05 9:39 ` martin rudalics
2021-09-05 9:42 ` Eli Zaretskii
2021-09-06 8:31 ` martin rudalics
2021-09-05 16:13 ` Juri Linkov
2021-09-05 16:47 ` Eli Zaretskii
2021-09-06 8:31 ` martin rudalics
2021-09-06 10:57 ` Eli Zaretskii
2021-09-06 14:08 ` martin rudalics
2021-09-06 15:43 ` Eli Zaretskii
2021-09-06 15:10 ` Juri Linkov
2021-09-12 16:32 ` Juri Linkov
2021-09-02 18:46 ` martin rudalics
2021-09-03 8:10 ` Juri Linkov
2021-09-02 15:59 ` Eli Zaretskii
2021-09-01 15:42 ` Juri Linkov
2021-09-01 19:26 ` Eli Zaretskii
2021-09-01 12:02 ` Eli Zaretskii
2021-09-01 15:44 ` Juri Linkov
2021-09-01 16:12 ` Eli Zaretskii
2021-09-01 16:25 ` Juri Linkov
2021-09-12 17:12 ` Juri Linkov
2021-09-12 17:32 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d650967e-235b-c40e-810f-6aed40f57d46@gmx.at \
--to=rudalics@gmx.at \
--cc=50256@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.