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: Thu, 07 Jul 2016 19:48:12 +0300 [thread overview]
Message-ID: <83wpkxjsxf.fsf@gnu.org> (raw)
In-Reply-To: <874m8176zx.fsf@gmx.net> (message from Stephen Berman on Thu, 07 Jul 2016 18:22:42 +0200)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: npostavs@users.sourceforge.net, 23478@debbugs.gnu.org
> Date: Thu, 07 Jul 2016 18:22:42 +0200
>
> What do you understand by "selection backward"?
mouse-select-region-backward can be interpreted as "mouse selects
region backward".
> My intention was to indicate that this variable controls selecting
> the region when you double-click at region-end
But "region-end" doesn't appear in the name.
How about mouse-select-region-at-region-end ?
> >> One somewhat embarassing aspect of describing this option is that is
> >> makes the default asymmetrical behavior painfully obvious without
> >> providing a rationale for it (and I don't know of any). I suppose we
> >> could add "for historical reasons" after "by default"....
> >
> > I don't think it's needed: since point doesn't move, no scrolling
> > should be expected.
>
> What's not needed: the phrase "for historical reasons", a rationale for
> the asymmetrical behavior, or any description of the user option? In
> other words, are you saying the doc changes in the patch are acceptable?
The rationale is not needed, IMO.
next prev parent reply other threads:[~2016-07-07 16:48 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wpkxjsxf.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 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.