From: Adam Funk <a24061@yahoo.com>
Subject: Re: Typing and pasting "special" characters directly in emacs in xterm?
Date: Wed, 11 Oct 2006 11:11:29 +0100 [thread overview]
Message-ID: <hjsuv3-43h.ln1@news.ducksburg.com> (raw)
In-Reply-To: 87r6xfeog1.fsf@thalassa.informatimago.com
On 2006-10-10, Pascal Bourguignon <pjb@informatimago.com> wrote:
> The second way is to assume a 7-bit ASCII keyboard, and to use the 8th
> bit to indicate when Meta is pressed.
>
> M-d is then transmited as the byte 228 (100 + 8th bit set).
>
> Unfortunately, if you have an ISO-8859-1 or ISO-8859-15 keyboard, the
> byte 228 is the ISO-8859-1/15 character ä.
>
> So when you type ä, you send 228, and emacs interprets that as M-d,
> which will delete the following word.
OK, now I understand why it's going wrong!
> So, you should configure your terminal to send ESC for Meta instead of
> setting the high bit. Then you can use the high bit to send
> ISO-8859-15 character codes instead of ASCII+Meta.
>
> You can do that editing ~/.Xresources or with Control-<MouseLeftDown>
> in the xterm window to display a menu and select "Meta Sends Escape".
I've just tried the second suggestions and I'm still getting the same
results (over ssh and locally). I'll look at the .Xresources stuff
later.
> Mind setting the various LC_* environment variables to indicate the
> encoding you use.
>
> You can also use a UTF-8 aware terminal, to be able to display and
> enter characters out of the ISO-8859-15 character set.
I thought xterm *was* UTF-8 aware --- at least, when I'm typing in it
other than in emacs, the "non-US" characters appear normally.
Thanks very much --- I haven't solved the problem yet but at least now
I have a good idea of what the problem is.
next prev parent reply other threads:[~2006-10-11 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 16:45 Typing and pasting "special" characters directly in emacs in xterm? Adam Funk
2006-10-10 23:33 ` Pascal Bourguignon
2006-10-11 10:11 ` Adam Funk [this message]
2006-10-12 16:03 ` Adam Funk
2006-10-18 3:45 ` Din
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=hjsuv3-43h.ln1@news.ducksburg.com \
--to=a24061@yahoo.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.
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).