From: Alan Third <alan@idiocy.org>
To: Andrew Hyatt <ahyatt@gmail.com>
Cc: 5011@debbugs.gnu.org, Jules Colding <colding@42tools.com>
Subject: bug#5011: 23.1.50; The {}\ characters seems to be impossible to write in non-terminal mode on Mac OS X
Date: Tue, 17 May 2016 20:35:53 +0100 [thread overview]
Message-ID: <m2mvno5vfq.fsf@breton.holly.idiocy.org> (raw)
In-Reply-To: <m2twjruygz.fsf@gmail.com> (Andrew Hyatt's message of "Sun, 27 Mar 2016 22:29:16 -0400")
Andrew Hyatt <ahyatt@gmail.com> writes:
> Sorry for the late reply, but I'm assuming this must be with a keyboard
> that doesn't have a \, {, or }. Which keyboard do you have, and how
> have you set things up so that S-Alt-7,8, or 9 produce these characters?
> How can I reproduce this on a standard US keyboard?
Hi Andrew, this is a clash between OS X's keymap and Emacs's.
On an Apple UK keyboard if you type shift-3 you get £ (pound sterling
symbol, in case it doesn't show), but # is on the same key, so you have
to type option-3 to get it. Emacs treats option as Meta and therefore in
Emacs typing option-3 results in the next command being repeated 3 times
and no # symbol.
I think the reported bug is exactly the same problem but on a different
keyboard layout.
There are a number of work-arounds including making the command key meta
instead of option, or unbinding the right option key so Emacs ignores it
and OS X's binding works, but leaving left-option bound to meta.
None of them strike me as being an obvious candidate for the default,
but the current behaviour is not good either.
--
Alan Third
prev parent reply other threads:[~2016-05-17 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 13:29 bug#5011: 23.1.50; The {}\ characters seems to be impossible to write in non-terminal mode on Mac OS X Jules Colding
2016-03-28 2:29 ` Andrew Hyatt
2016-05-17 19:35 ` Alan Third [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2mvno5vfq.fsf@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=5011@debbugs.gnu.org \
--cc=ahyatt@gmail.com \
--cc=colding@42tools.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 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.