GNU bug report logs - #19513
shift-select-mode fails to be fully buffer-local

Previous Next

Package: emacs;

Reported by: Kelly Dean <kelly <at> prtime.org>

Date: Mon, 5 Jan 2015 01:08:02 UTC

Severity: minor

Fixed in version 25.1

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #14 received at 19513 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
To: Kelly Dean <kelly <at> prtime.org>
Cc: 19513 <at> debbugs.gnu.org
Subject: Re: bug#19513: shift-select-mode fails to be fully buffer-local
Date: Tue, 06 Jan 2015 10:24:01 -0500
> Comment out lines 384-385 to enable it to work with shift-select-mode, to see how the latter interferes.
> Enable the mode, then press S-down.  Then press down, and since you're
> doing a non-shifted motion command following a shifted motion command,
> shift-select-mode deactivates the region.

I'm not sure it should be considered as a bug, or at least one specific
to line-select-minor-mode.

The same behavior shows up if you do (in "emacs -Q"):

  C-SPC next S-next

and you see that the S-next ended the previous selection and started
a new one.  Some might see it as a feature (I don't know if it was
implemented this way on purpose or by accident).

If we see it as a bug the right answer is probably to change
shift-select-mode such that shifted-motion doesn't start a new
shift-selection if we're already in the middle of an
"old-style" selection.

Since you have shift-select-mode disabled globally, you shouldn't
care anyway, so I guess you're doing this in response to complaints from
users of vimizer.  If so, do they usually use shift-select-mode?
If not, maybe the right answer is to tell them they should disable
shift-select-mode.


        Stefan




This bug report was last modified 8 years and 97 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.