From: storm@cua.dk (Kim F. Storm)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Dan Nicolaescu <dann@ics.uci.edu>, emacs-devel@gnu.org
Subject: Re: [Dan Nicolaescu] S-arrow_keys not working in cua-selection-mode anymore
Date: Thu, 15 Nov 2007 13:52:36 +0100 [thread overview]
Message-ID: <874pfnr7qj.fsf@kfs-lx.testafd.dk> (raw)
In-Reply-To: <jwvpryc27hc.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed\, 14 Nov 2007 10\:14\:07 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> I'll do it.
>
Thanks.
>
> I understand the need for the tty version of the code, but I'm wondering
> why that branch can't be used equally well for the window-system case.
> I.e. I suggest the code below instead:
>
> ((or
> (memq 'shift (event-modifiers
> (aref (this-single-command-keys) 0)))
> ;; See if raw escape sequence maps to a shifted event, e.g. S-up or C-S-home.
> (let ((ev (lookup-key input-decode-map
> (this-single-command-raw-keys))))
> (if (vector ev)
> (and (symbolp (setq ev (aref ev 0)))
> (string-match "S-" (symbol-name ev)))
> (memq 'shift (event-modifiers
> (aref (this-single-command-raw-keys) 0))))))
>
It might work, yes, but the window system code is faster, simpler, and
has worked fine (at least in my experience).
So I don't see a reason to go through the "tricky -nw path" also on
window systems ... just to end up doing the same thing as before.
But perhaps there us some benefit of going through input-decode-map
also on window systems?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2007-11-15 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 14:32 [Dan Nicolaescu] S-arrow_keys not working in cua-selection-mode anymore Kim F. Storm
2007-11-13 15:20 ` Stefan Monnier
2007-11-14 11:45 ` Kim F. Storm
2007-11-14 15:14 ` Stefan Monnier
2007-11-15 12:52 ` Kim F. Storm [this message]
2007-11-15 16:36 ` Stefan Monnier
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=874pfnr7qj.fsf@kfs-lx.testafd.dk \
--to=storm@cua.dk \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.