From: David Kastrup <dak@gnu.org>
Subject: Re: umlauts (8bit characters) input
Date: Tue, 01 Feb 2005 17:05:40 +0100 [thread overview]
Message-ID: <x5is5ctgdn.fsf@lola.goethe.zz> (raw)
In-Reply-To: cto8g8$kjt$03$2@news.t-online.com
Hendrik Sattler <sattler2000@gmx.de> writes:
> lisp/term/linux.el did some more than nothing:
> ;; The Linux console handles Latin-1 by default.
> (unless (terminal-coding-system)
> (set-terminal-coding-system 'iso-latin-1))
>
> ;; Make Latin-1 input characters work, too.
> ;; Meta will continue to work, because the kernel
> ;; turns that into Escape.
> (let ((value (current-input-mode)))
> ;; The third arg only matters in that it is not t or nil.
> (set-input-mode (nth 0 value) (nth 1 value) 'iso-latin-1 (nth 3 value)))
>
> I just copied it over to my ~/.emacs and it works now. So, to correct David,
> emacs does obviously NOT follow locales idea of character set (at least not
> for everything).
> Maybe in my previous installation, I just had TERM fixed to "linux" to solve
> this, I just don't remember...
>
> But you are right: maybe emacs gets to point where it magically
> "just works".
I have just verified that the development version of Emacs will start
up 8-bit transparent if the LC_CTYPE locale is indicating an 8-bit
character set. So this will work out of the box with Emacs-21.4.
I am afraid that I have not been able to find the manual methods from
term/linux.el in the Emacs-21.3 manual, though I am pretty sure that
at one point of time, the above somewhat arcane way via set-input-mode
was described there. Maybe the documentation changed faster than the
code.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-02-01 16:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 16:44 umlauts (8bit characters) input Hendrik Sattler
2005-01-31 21:52 ` Peter Dyballa
[not found] ` <mailman.226.1107211155.2841.help-gnu-emacs@gnu.org>
2005-01-31 22:44 ` Hendrik Sattler
2005-01-31 23:47 ` Peter Dyballa
[not found] ` <mailman.238.1107216437.2841.help-gnu-emacs@gnu.org>
2005-02-01 0:41 ` Hendrik Sattler
2005-02-01 10:31 ` Peter Dyballa
[not found] ` <mailman.279.1107254715.2841.help-gnu-emacs@gnu.org>
2005-02-01 11:37 ` Hendrik Sattler
2005-02-01 12:36 ` David Kastrup
2005-02-01 13:37 ` Hendrik Sattler
2005-02-01 15:25 ` Peter Dyballa
2005-02-02 10:27 ` Peter Dyballa
[not found] ` <mailman.463.1107343604.2841.help-gnu-emacs@gnu.org>
2005-02-02 12:38 ` David Kastrup
2005-02-02 13:12 ` Peter Dyballa
[not found] ` <mailman.482.1107350962.2841.help-gnu-emacs@gnu.org>
2005-02-02 14:10 ` David Kastrup
2005-02-02 14:59 ` Ismael Valladolid Torres
2005-02-02 18:21 ` Peter Dyballa
2005-02-02 18:17 ` Peter Dyballa
2005-02-02 15:19 ` Stefan Monnier
2005-02-02 19:37 ` Peter Dyballa
[not found] ` <mailman.578.1107374620.2841.help-gnu-emacs@gnu.org>
2005-02-03 4:09 ` Stefan Monnier
2005-02-01 13:07 ` Reiner Steib
2005-02-01 13:47 ` Hendrik Sattler
2005-02-01 15:21 ` Peter Dyballa
2005-02-01 15:50 ` Hendrik Sattler
2005-02-01 16:05 ` David Kastrup [this message]
2005-02-01 16:08 ` Hendrik Sattler
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=x5is5ctgdn.fsf@lola.goethe.zz \
--to=dak@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.
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).