From: Julian Rohrhuber via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 47360@debbugs.gnu.org
Subject: bug#47360: 27.1; using 'bar cursor, mouseclick is rounded to the wrong char position
Date: Sun, 28 Mar 2021 13:00:50 +0000 [thread overview]
Message-ID: <C4B209A0-9693-40E7-A009-A48BFA0C9C39@protonmail.com> (raw)
In-Reply-To: <83eefzoi3k.fsf@gnu.org>
> On 28. Mar 2021, at 09:25, Eli Zaretskii <eliz@gnu.org> wrote:
>
>>
>> Date: Sun, 28 Mar 2021 07:15:38 +0000
>> From: Julian Rohrhuber <rohrhuber@protonmail.com>
>> Cc: larsi@gnus.org, 47360@debbugs.gnu.org
>>
>>
>>>> There is one more case where one can feel the difference: when selecting with the mouse and dragging to the right, the selection jumps to each character a little "too late", that is, after you have already crossed the position you want the selection to end at. You have to point to a character *after* the one you want to include. The current selection always is up to one character behind the cursor barline. This results in a "sticky" feeling.
>>>
>>> Yes, selection in Emacs works on per-character granularity, because it
>>> uses the faces infrastructure. We'd need to do something very
>>> different to make that use pixel granularity. Patches are welcome.
>>
>> I don't think that a change of granularity would be necessarily at all to improve what I describe. All what would have to be done is to change at what *cursor* position the selection jumps to the next character (namely when it crosses its middle). So it would only another application of the solution to the current issue.
>
> Sorry, I thought you were talking about the jumps, not about when the
> jump is done.
>
> However, with your proposal, the jump will be too early, so instead of
> "lagging" the selection would sometimes "lead" the mouse pointer,
> i.e. be ahead of it. As long as the changes are one character at a
> time, there's no way around that basic fact.
Yes, it will still be off -- but only half as far. This makes a big difference in terms of interaction.
Checking other editors, they do it the same, and I think that is what is the "expected behaviour".
prev parent reply other threads:[~2021-03-28 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 7:42 bug#47360: 27.1; using 'bar cursor, mouseclick is rounded to the wrong char position Julian Rohrhuber via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-24 17:25 ` Eli Zaretskii
2021-03-24 17:38 ` Julian Rohrhuber via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-24 18:25 ` Eli Zaretskii
2021-03-24 18:39 ` Lars Ingebrigtsen
2021-03-24 19:08 ` Julian Rohrhuber via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-27 17:53 ` Julian Rohrhuber via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-27 19:47 ` Eli Zaretskii
2021-03-28 7:15 ` Julian Rohrhuber via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-28 7:25 ` Eli Zaretskii
2021-03-28 13:00 ` Julian Rohrhuber via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=C4B209A0-9693-40E7-A009-A48BFA0C9C39@protonmail.com \
--to=bug-gnu-emacs@gnu.org \
--cc=47360@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=rohrhuber@protonmail.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).