From: "Eric M. Ludlam" <eric@siege-engine.com>
Cc: emacs-devel@gnu.org
Subject: Re[2]: 8 bit input chars on tty broken
Date: Fri, 19 Jul 2002 12:47:02 -0400 [thread overview]
Message-ID: <200207191647.g6JGl2k07543@beta.siege-engine.com> (raw)
In-Reply-To: <200207191340.g6JDebJ15674@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)
>>> "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> seems to think that:
>> I got a new CVS build running a couple days ago (21.3.50.1) after
>> running 21.1.x for quite some time. In the transition, 8 bit input
>> chars on a TTY lost their meta-ness. Thus, I press ALT-X which
>> creates an 8 bit character, and it inserts a circle with a line
>> through it instead of providing my favorite prompt.
>
>What happens if you do the same ALT-X in another application (like bash) ?
>What happens if you use something like Multi_key a o (which should
>insert a latin-1 å if you) or use some other non-Emacs input method
>to type a latin-1 char (in bash and in Emacs) ?
>What terminal is it ? What are your locale setting ?
Emacs 21.1 created the M-x prompt. Tcsh also creates the funny
characters.
>The reason you see this, is mentioned in the NEWS file:
>
> ** The keyboard-coding-system is now automatically set based on
> your current locale settings. If it turns out that your terminal
> does not support the encoding implied by your locale (for example,
> it inserts non-ASCII chars if you hit M-i), you will need to add
>
> (set-keyboard-coding-system nil)
>
> to your .emacs to revert to the old behavior.
[ ... ]
You are right. This fixed my 8 bit meta-ness. I did not see it when
looking through the news file as I was using search keywords such as
"8" "input" and some other terms I remember being used for this type
of thing.
My environment from the SHELL buffer has this in it (after removing
useless stuff):
TERM=dumb
TERMCAP=
COLUMNS=80
EMACS=t
HOME=/home/zappo
OSTYPE=linux
HOSTTYPE=i386-linux
SHELL=/bin/tcsh
SUPPORTED=en_US:en
LANG=en_US
It looks like SUPPORTED/LANG is possibly involved, but it seems odd
to remove support for US English to get meta back.
Thanks for the quick response. I was putting a lot of funny
characters in my buffers.
Eric
--
Eric Ludlam: zappo@gnu.org, eric@siege-engine.com
Home: www.ultranet.com/~zappo Siege: www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: www.gnu.org
next prev parent reply other threads:[~2002-07-19 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 12:56 8 bit input chars on tty broken Eric M. Ludlam
2002-07-19 13:40 ` Stefan Monnier
2002-07-19 16:47 ` Eric M. Ludlam [this message]
2002-07-21 5:31 ` Re[2]: " Eli Zaretskii
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=200207191647.g6JGl2k07543@beta.siege-engine.com \
--to=eric@siege-engine.com \
--cc=emacs-devel@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).