all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stephen Berman <stephen.berman@gmx.net>, Eli Zaretskii <eliz@gnu.org>
Cc: 23478@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#23478: 25.0.93; Mouse region selection asymmetry
Date: Mon, 4 Jul 2016 15:29:54 +0000 (UTC)	[thread overview]
Message-ID: <3c435aac-aab0-46b6-97a7-4a90badfafea@default> (raw)
In-Reply-To: <87wpl17pvs.fsf@gmx.net>

> If by "it" you mean the new behavior, then I agree nobody needs it, in
> the sense that it doesn't provide any functionality you can't get
> another way (e.g. by selecting a region by means of key combinations by
> dragging the mouse instead of by double-clicking).  Nevertheless, I've
> always been slightly annoyed when I've encountered the issue, just never
> enough to try and do anything about it till now.
> 
> >> I think opting in is best in cases where it's
> >> likely that some people may prefer (or some code may depend on) the
> >> existing behavior, or where the new behavior may bring a disadvantage in
> >> some case.  But I don't think any of that is likely in this case
> >> (indeed, I really think the existing behavior is a misfeature).  Your
> >> concern about the interaction with scroll-conservatively applied to my
> >> initial patch, but you yourself suggested a better alternative that
> >> allays this concern.  Given that, I ask again, and not rhetorically, do
> >> you see a strong downside to having the new behavior be the default?
> >
> > Let's make one step back and describe the exact change in behavior
> > with the last patch, OK?  Maybe some of us (e.g., me) don't really
> > understand what is the change.
> 
> It simply makes selecting a region by double-clicking with the mouse
> more uniform; as I wrote in my OP, the current behavior is this:
> 
>    When you select a region by double-clicking with mouse-1 and the end
>    of the region is below the last visible line of the window, Emacs
>    recenters the display, making the entire selected region visible
>    (unless it's larger than half the window's height).  But when you
>    select a region by double-clicking with mouse-1 and the beginning of
>    the region is above the first visible line of the window, Emacs does
>    not recenter the display, so the entire selected region is not
>    visible.
> 
> With the patch the behavior is now simply this:
> 
>    When you select a region by double-clicking with mouse-1, Emacs
>    recenters the display, making the entire selected region visible
>    (unless it's larger than half the window's height).
> 
> To me (and I think Noam agrees), this is the behavior I would expect,
> while the current behavior is less user-friendly; I can't think of a
> reason why anyone would dislike the new behavior or prefer the current
> behavior, but maybe someone can provide a use case.

I haven't really been following this thread.  Now that I've read
the summary description of the problem (I have not tried the fix),
here are my two cents, FWIW.

1. I agree with Eli about new features generally being opt-in, not
   opt-out.  Actually, he spoke of "backward-incompatible behavior",
   and I agree with that "almost always" approach too:

   "I think backward-incompatible behavior should almost always be
    opt-in, unless we have no choice."

2. I see plenty of _bug fixes_ that have backward-incompatible
   behavior, and that are neither opt-in nor "have no choice".
   No, I'm not going to look for a list of them.  But this is
   definitely my recollection and impression.  (And it is usually
   not a problem - I am not complaining that it is here.)

3. In this particular case, I agree with Stephen.  I really don't
   see why someone would complain about this fix.  And if someone
   does then it should be easy enough to discuss and DTRT at that
   point.

4. Also in this case, as Eli said, this is not a big deal either
   way.  But I see (so far) no reason for keeping both behaviors
   and providing a user choice here.  If the non-recentering
   behavior were the case for both directions then I can imagine
   that someone might argue for a choice (recenter or not).  But
   I don't think that will happen here.

In sum, FWIW my vote would be to fix this unconditionally, and
not bother with a user option for this.

(This should apply only to the case where the entire region _can_
be shown in the window, of course.  If it cannot (too big), then
there is little reason to recenter.)





  parent reply	other threads:[~2016-07-04 15:29 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
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 [this message]
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=3c435aac-aab0-46b6-97a7-4a90badfafea@default \
    --to=drew.adams@oracle.com \
    --cc=23478@debbugs.gnu.org \
    --cc=eliz@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.