From: ludo@chbouib.org (Ludovic Courtès)
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: rms@gnu.org, Kenichi Handa <handa@m17n.org>,
ludovic.courtes@laas.fr, emacs-devel@gnu.org,
435452@bugs.debian.org, svenjoac@gmx.de
Subject: Re: Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode]
Date: Sat, 01 Sep 2007 12:09:58 +0200 [thread overview]
Message-ID: <87hcmeu26h.fsf@chbouib.org> (raw)
In-Reply-To: <jwvwsvblqoh.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri\, 31 Aug 2007 10\:36\:16 -0400")
Hi,
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> Typing M-x yields the `ø' ("o slash") character instead of running
>> `execute-extended-command'.
>
> This is because your terminal sends the exact same byte sequence (in this
> case it's actually a single byte) when you type M-x as when you type ø, so
> Emacs has no way to distinguish the two: it chooses to interpret the byte as
> ø here (which messes up the M-x case) and you could tell it to interpret it
> as M-x (which would mess up the ø case).
I see, thanks for the clarification!
> Indeed, that's the right solution because it tells your Terminal to use
> different byte-sequences for the two different cases.
Understood.
Thanks,
Ludovic.
prev parent reply other threads:[~2007-09-01 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1IPQsY-0001cQ-K1@fencepost.gnu.org>
[not found] ` <E1IPwDo-000119-9m@etlken.m17n.org>
[not found] ` <87y7fvbp6r.fsf_-_@gmx.de>
2007-08-29 20:05 ` Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode] ludo, Ludovic =?UTF-8?Q?Court=C3=A8s
2007-08-30 1:08 ` Kenichi Handa
2007-08-30 20:55 ` ludo, Ludovic =?UTF-8?Q?Court=C3=A8s
2007-08-31 14:36 ` Stefan Monnier
2007-09-01 10:09 ` Ludovic Courtès [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=87hcmeu26h.fsf@chbouib.org \
--to=ludo@chbouib.org \
--cc=435452@bugs.debian.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=ludovic.courtes@laas.fr \
--cc=monnier@IRO.UMontreal.CA \
--cc=rms@gnu.org \
--cc=svenjoac@gmx.de \
/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.