From: Mikhail Gusarov <dottedmag@dottedmag.net>
To: 21330@debbugs.gnu.org
Subject: bug#21330: Acknowledgement ([PATCH] Fix handling Command-Control-<letter> combination under OS X)
Date: Sun, 23 Aug 2015 18:51:35 +0200 [thread overview]
Message-ID: <1440348695.1745750.363703345.5F61D85B@webmail.messagingengine.com> (raw)
In-Reply-To: <handler.21330.B.144034859519108.ack@debbugs.gnu.org>
A copy of commit message for easier handling:
Do not use [theEvent characters] for getting key if Command is supplied,
this causes Command-Control-A and similar key combinations to be
interpreted as control characters (^A), which breaks key processing
later on. The code which produces wrong keycode claims to handle Dvorak,
but Dvorak keyboard is handled fine without it.
* src/nsterm.m (keyDown): Disable code consulting input manager, not
needed.
On Sun, 23 Aug 2015, at 18:50, GNU bug Tracking System wrote:
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> bug-gnu-emacs@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 21330@debbugs.gnu.org.
>
> Please do not send mail to help-debbugs@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 21330: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21330
> GNU Bug Tracking System
> Contact help-debbugs@gnu.org with problems
prev parent reply other threads:[~2015-08-23 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 16:49 bug#21330: [PATCH] Fix handling Command-Control-<letter> combination under OS X Mikhail Gusarov
[not found] ` <handler.21330.B.144034859519108.ack@debbugs.gnu.org>
2015-08-23 16:51 ` Mikhail Gusarov [this message]
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=1440348695.1745750.363703345.5F61D85B@webmail.messagingengine.com \
--to=dottedmag@dottedmag.net \
--cc=21330@debbugs.gnu.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).