From: Alan Third <alan@idiocy.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: adrian.b.robert@gmail.com, 19977@debbugs.gnu.org
Subject: bug#19977: 24.4; Incorrect translation of Super modifier with Ctrl or Meta on OS X
Date: Tue, 26 Dec 2017 21:16:03 +0000 [thread overview]
Message-ID: <20171226211603.GA82103@breton.holly.idiocy.org> (raw)
In-Reply-To: <CAArVCkTHM4H4favbCYQfQ=pmkb-Rk_+iT_XpE0yMG_t=SGu6dw@mail.gmail.com>
On Tue, Dec 26, 2017 at 08:14:59PM +0000, Philipp Stephani wrote:
> Alan Third <alan@idiocy.org> schrieb am Di., 26. Dez. 2017 um 18:42 Uhr:
>
> > Do you think this patch is still good?
> >
>
> I think so, modulo the caveats mentioned in the comments. Do you want me to
> rebase and commit it?
As far as I can tell from the comments with the patch installed we
should be no worse off than we are at the moment?
I can’t quite work this out from a quick look at the code, but is it
the case that when option or command is bound to meta or super then it
acts as a control‐like modifier, but when it’s unbound then it acts as
a shift‐like modifier?
So this should give us the same behaviour for both keys that we have
with option just now?
> > I reckon the issues with command-key modifiers should be fixed, even if
> > it's just a new variable that disables the shift-like behaviour of
> > command.
> >
> >
> Do you mean "should be fixed" as in "I believe it's fixed" or as in "I want
> it to be fixed, but it's not yet fixed"?
Definitely the latter.
> If the latter, I'm not sure whether the macOS event model allows us to do
> this. As mentioned in the comments in the patch, some information just
> appears to be lost entirely.
I recently found myself using this lovely binding:
(define-key global-map [C-s-268632064]
'ns-do-show-character-palette)
and it seems crazy to me that the default behaviour of Emacs requires
us to use 268632064 instead of SPC when we could tell people using
unusual keyboard layouts to set a variable or something instead.
As for losing data, as long as it’s no worse than what we have at the
moment, which I believe you said is the case in a previous email, then
I don’t see a problem with that.
But perhaps I’ve misunderstood and there’s some worse behaviour?
Thanks!
--
Alan Third
next prev parent reply other threads:[~2017-12-26 21:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 16:36 bug#19977: 24.4; Incorrect translation of Super modifier with Ctrl or Meta on OS X Philipp Stephani
2016-03-29 10:17 ` Philipp Stephani
2016-03-29 15:10 ` Eli Zaretskii
2016-03-29 15:29 ` Philipp Stephani
2016-03-29 15:45 ` Philipp Stephani
2016-03-29 15:59 ` Eli Zaretskii
2016-03-29 16:31 ` Philipp Stephani
2016-03-29 16:38 ` Philipp Stephani
2016-03-29 16:57 ` Eli Zaretskii
2016-03-29 17:19 ` Adrian Robert
2016-03-29 17:44 ` Philipp Stephani
2016-03-29 17:56 ` Adrian Robert
2016-03-29 19:43 ` Philipp Stephani
2016-03-29 20:07 ` Philipp Stephani
2016-03-30 2:39 ` Eli Zaretskii
2016-03-30 17:35 ` Philipp Stephani
2017-12-26 17:42 ` Alan Third
2017-12-26 20:14 ` Philipp Stephani
2017-12-26 21:16 ` Alan Third [this message]
2018-02-04 19:07 ` Philipp Stephani
2018-02-04 20:18 ` Alan Third
2018-02-05 8:02 ` Philipp Stephani
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=20171226211603.GA82103@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=19977@debbugs.gnu.org \
--cc=adrian.b.robert@gmail.com \
--cc=p.stephani2@gmail.com \
/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).