From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: UTF-8 and M-x shell?
Date: Sun, 08 Feb 2004 14:33:55 +0100 [thread overview]
Message-ID: <87ekt5vgos.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: 20040208102520.213b4a20.occitan@esperanto.org
Daniel Pfeiffer <occitan@esperanto.org> writes:
> I'm migrating my Gnu/Linux to LANG=de_DE.UTF-8 and finding that I need to
> recode my old Latin-9 filenames.
>
> But now Gnu Emacs (2-3 weeks old CVS) M-x shell gets problems.
> First off, the buffer still comes up in Latin-1. That can
> apparently be fixed with (set-language-environment "utf-8"), but
> only interactively, not in .emacs.el!
Strange. What happens if you put (set-language-environment "utf-8")
into ~/.emacs? Is there an error message?
> But it doesn't help:
>
> - M-! umlaut-emitting-command displays old (1-byte) umlauts as octal
> and utf-8 correctly
That's how it is supposed to be.
> - but with the same commands in the shell buffer, with mode-line u:, it still
> displays everything as one-byte.
What does M-x describe-coding-system RET RET say when in the shell
buffer? The codings for process i/o should be utf-8. As a
workaround, you could try M-: (set-process-coding-system nil 'utf-8
'utf-8) RET from the *shell* buffer.
> What must I do for M-x shell to respect $LANG, like an xterm?
>
> (Btw. before I had LANG=de_DE@euro, which is Latin-9, but Emacs wrongly
> defaulted to Latin-1 -- which luckily is quite similar.)
That's also strange -- my Emacs defaulted to Latin-9 when I did this.
Maybe it was a font problem? I had set "Emacs.font:
yadda-yadda-iso8859-15" originally, but had to revert to "Emacs.font:
yadda-yadda-iso8859-1" to get the right behavior.
Kai
next prev parent reply other threads:[~2004-02-08 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 9:25 UTF-8 and M-x shell? Daniel Pfeiffer
2004-02-08 13:33 ` Kai Grossjohann [this message]
2004-02-08 21:09 ` Daniel Pfeiffer
2004-02-08 18:15 ` 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=87ekt5vgos.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.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.
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).