From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: user42_kevin@yahoo.com.au, 26396@debbugs.gnu.org
Subject: bug#26396: 25.1; char-displayable-p on a latin1 tty
Date: Mon, 17 Apr 2017 09:24:22 +0300 [thread overview]
Message-ID: <83vaq3eell.fsf@gnu.org> (raw)
In-Reply-To: <2685c665-652c-644a-9550-e0e283d9f315@cs.ucla.edu> (message from Paul Eggert on Sun, 16 Apr 2017 20:26:01 -0700)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 16 Apr 2017 20:26:01 -0700
>
> Kevin Ryde wrote:
>
> > Debian has an easy line in /etc/default/console-setup. The default is
> > now utf8 but there's lots more. I have it latin1.
>
> In that case I stand corrected: some people are stull using non-UTF-8 Linux
> consoles. I don't know of any convenient programmatic way for Emacs to determine
> whether the console is in UTF-8 output mode, though. (I can think of complicated
> ways, involving outputting bytes to the screen and seeing what happens to the
> cursor position; but this would be destructive to the screen contents.) I agree
> Emacs shouldn't be changing the mode.
I agree.
Regarding testing it, the simplest way is to provide a user variable
which will tell Emacs about the console's mode, and ask users who
don't want the UTF-8 mode to set that variable to that effect. Or
maybe my idea about using terminal-coding-system as an indication of
that could be workable, in which case it's a better alternative.
WDYT?
I can offer help in reviewing the patches and perhaps also writing
some of that, but I cannot test the code, as I don't have a convenient
access to a Linux console where I could run Emacs I build.
TIA
next prev parent reply other threads:[~2017-04-17 6:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 2:20 bug#26396: 25.1; char-displayable-p on a latin1 tty Kevin Ryde
2017-04-08 7:42 ` Eli Zaretskii
2017-04-09 5:16 ` Kevin Ryde
2017-04-10 6:47 ` Eli Zaretskii
2017-04-10 7:05 ` Eli Zaretskii
2017-04-10 7:45 ` Eli Zaretskii
2017-04-13 6:19 ` Paul Eggert
2017-04-13 7:16 ` Eli Zaretskii
2017-04-13 20:58 ` Paul Eggert
2017-04-14 3:01 ` Kevin Ryde
2017-04-14 18:59 ` Paul Eggert
2017-04-14 12:37 ` Eli Zaretskii
2017-04-14 18:56 ` Paul Eggert
2017-04-15 8:48 ` Eli Zaretskii
2017-04-15 21:12 ` Paul Eggert
2017-04-16 5:59 ` Eli Zaretskii
2017-04-16 20:25 ` Paul Eggert
2017-04-17 6:19 ` Eli Zaretskii
2017-04-17 3:00 ` Kevin Ryde
2017-04-17 3:26 ` Paul Eggert
2017-04-17 5:56 ` Paul Eggert
2017-04-17 7:33 ` Eli Zaretskii
2017-04-17 17:22 ` Paul Eggert
2017-04-17 6:24 ` Eli Zaretskii [this message]
2017-04-17 6:41 ` Paul Eggert
2017-04-17 7:27 ` Kevin Ryde
2017-04-17 8:08 ` Eli Zaretskii
2017-04-17 18:08 ` Paul Eggert
2017-04-17 18:32 ` Eli Zaretskii
2017-04-18 17:49 ` Paul Eggert
2017-04-18 18:19 ` Eli Zaretskii
2017-04-13 22:07 ` Richard Stallman
2017-04-13 22:18 ` Paul Eggert
2017-04-14 19:48 ` Richard Stallman
2017-04-11 7:22 ` Kevin Ryde
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=83vaq3eell.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26396@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=user42_kevin@yahoo.com.au \
/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).