From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 36550@debbugs.gnu.org, linus.kallberg@outlook.com
Subject: bug#36550: mouse-face overlay calculation error
Date: Sat, 13 Jul 2019 17:17:54 +0300 [thread overview]
Message-ID: <83zhliyq5p.fsf@gnu.org> (raw)
In-Reply-To: <m3d0ieoxfy.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 13 Jul 2019 15:50:41 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 36550@debbugs.gnu.org, linus.kallberg@outlook.com
> Date: Sat, 13 Jul 2019 15:50:41 +0200
>
> commit 5d24c60e3a3b07ccb31b886885ea117a058168be
> Author: David Ponce <david@dponce.com>
> Date: Mon Apr 3 14:34:28 2006 +0000
>
> (recentf-open-files-item): Include newline in button
> field, so opening a file will work, when the point is at the end
> of the file name. Allow, for example, to [i]search a file by
> extension and just push RET to open it.
>
> So it really wants the widget to have the newline inside the widget for
> usability reasons.
I still don't understand why. Surely, "the end of the file name" is
before the newline, right? And what point has to do with that, since
mouse-face is about the mouse pointer, not about point? What am I
missing here?
> Well, it's not 100% right, since it highlights the first character on
> the next line if you have mouse-face on the preceding newline, which has
> to be a bug even if we're not supposed to put mouse-face on the newline.
> :-)
No, it's 100% right, because it implements a certain set of
requirements, and those mandate that when the end point is beyond the
last character on a line, that end point is in the next line.
next prev parent reply other threads:[~2019-07-13 14:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 12:54 bug#36550: Small bug fix in recentf.el Linus Källberg
2019-07-08 19:58 ` Lars Ingebrigtsen
[not found] ` <AM0PR09MB2867529A5BCE4551365F142C87F60@AM0PR09MB2867.eurprd09.prod.outlook.com>
2019-07-09 13:04 ` Lars Ingebrigtsen
2019-07-11 16:34 ` Linus Källberg
2019-07-12 15:07 ` Lars Ingebrigtsen
2019-07-13 0:31 ` bug#36550: mouse-face overlay calculation error Lars Ingebrigtsen
2019-07-13 6:15 ` Eli Zaretskii
2019-07-13 13:10 ` Lars Ingebrigtsen
2019-07-13 13:23 ` Eli Zaretskii
2019-07-13 13:50 ` Lars Ingebrigtsen
2019-07-13 14:17 ` Eli Zaretskii [this message]
2019-07-13 14:25 ` Lars Ingebrigtsen
2019-07-13 14:50 ` Eli Zaretskii
2019-07-13 15:05 ` Lars Ingebrigtsen
2019-07-13 15:08 ` Lars Ingebrigtsen
2019-07-13 15:38 ` Linus Källberg
2019-07-13 15:49 ` Eli Zaretskii
2019-07-13 19:49 ` Linus Källberg
2019-07-14 5:30 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zhliyq5p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36550@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=linus.kallberg@outlook.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).