From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 23478@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#23478: 25.0.93; Mouse region selection asymmetry
Date: Sun, 03 Jul 2016 18:38:39 +0300 [thread overview]
Message-ID: <83furqratc.fsf@gnu.org> (raw)
In-Reply-To: <87poqun63w.fsf@gmx.net> (message from Stephen Berman on Sun, 03 Jul 2016 16:33:55 +0200)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, 23478@debbugs.gnu.org
> Date: Sun, 03 Jul 2016 16:33:55 +0200
>
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> >>> From: Stephen Berman <stephen.berman@gmx.net>
> >>> Do you really think this should be conditioned by a user option?
> >>
> >> I do, but let's hear from others. Anyone?
> >
> > This behaviour seems much preferable to me, since otherwise it's not
> > clear which text gets selected. I'm not in favour of adding an option,
> > but if there must be one, at least let this new behaviour be the
> > default.
>
> I agree on both points (prefer no option, but if so default to new).
>
> > Regarding the code, I notice that using (sit-for 0) works as well.
>
> Thanks. Indeed, even a negative number works. But zero does seem the
> least arbitrary.
>
> > A comment to explain what the calls are for would be nice.
>
> I'll do that when the final version is settled on. Eli, John, what's
> the decision on making this behavior customizable (and if yes, what
> default)?
I think backward-incompatible behavior should almost always be opt-in,
unless we have no choice.
next prev parent reply other threads:[~2016-07-03 15:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 15:44 bug#23478: 25.0.93; Mouse region selection asymmetry Stephen Berman
2016-05-08 16:23 ` Eli Zaretskii
2016-05-08 18:31 ` Stephen Berman
2016-05-08 18:54 ` Eli Zaretskii
2016-05-08 19:41 ` Stephen Berman
2016-05-08 19:45 ` Eli Zaretskii
2016-07-02 23:16 ` npostavs
2016-07-03 14:33 ` Stephen Berman
2016-07-03 15:38 ` Eli Zaretskii [this message]
2016-07-03 22:24 ` Stephen Berman
2016-07-04 2:38 ` Eli Zaretskii
2016-07-04 8:45 ` Stephen Berman
2016-07-04 14:57 ` Eli Zaretskii
2016-07-04 16:56 ` Stephen Berman
2016-07-04 18:26 ` Stephen Berman
2016-07-05 17:23 ` Eli Zaretskii
2016-07-06 16:40 ` Stephen Berman
2016-07-06 18:44 ` Eli Zaretskii
2016-07-07 12:08 ` Stephen Berman
2016-07-07 15:29 ` Eli Zaretskii
2016-07-07 16:22 ` Stephen Berman
2016-07-07 16:48 ` Eli Zaretskii
2016-07-07 17:02 ` Noam Postavsky
2016-07-07 17:16 ` Eli Zaretskii
2016-07-07 18:26 ` Stephen Berman
2016-07-08 9:58 ` Stephen Berman
2016-07-08 10:14 ` Eli Zaretskii
2016-07-08 15:38 ` Stephen Berman
2016-07-07 17:04 ` Stephen Berman
2016-07-04 15:29 ` Drew Adams
2016-07-05 1:32 ` npostavs
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=83furqratc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23478@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
--cc=stephen.berman@gmx.net \
/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).