From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Kelly Dean <kelly@prtime.org>
Cc: 19513@debbugs.gnu.org
Subject: bug#19513: shift-select-mode fails to be fully buffer-local
Date: Tue, 06 Jan 2015 10:24:01 -0500 [thread overview]
Message-ID: <jwvfvbo6isv.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <Ev9ue0eASBSrhmBKtOqgaCUE1LAC99oGkWDazaqjQ5Z@local> (Kelly Dean's message of "Tue, 06 Jan 2015 06:59:39 +0000")
> 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
next prev parent reply other threads:[~2015-01-06 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 1:06 bug#19513: shift-select-mode fails to be fully buffer-local Kelly Dean
2015-01-05 2:09 ` Stefan Monnier
2015-01-06 6:59 ` Kelly Dean
2015-01-06 15:24 ` Stefan Monnier [this message]
2015-01-06 19:20 ` Kelly Dean
2015-01-06 21:06 ` Stefan Monnier
2015-01-25 8:50 ` Kelly Dean
2015-01-25 15:16 ` Stefan Monnier
2015-01-26 4:16 ` Kelly Dean
2015-01-26 6:15 ` Eli Zaretskii
2015-01-25 15:40 ` Eli Zaretskii
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=jwvfvbo6isv.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=19513@debbugs.gnu.org \
--cc=kelly@prtime.org \
/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).