From: Kevin Ryde <user42_kevin@yahoo.com.au>
To: 26396@debbugs.gnu.org
Subject: bug#26396: 25.1; char-displayable-p on a latin1 tty
Date: Sat, 08 Apr 2017 12:20:57 +1000 [thread overview]
Message-ID: <87efx31vxy.fsf@blah.blah> (raw)
On a latin1 tty, char-displayable-p claims that almost all chars are
displayable, eg (char-displayable-p #x2022) => t.
I hoped when (terminal-coding-system) is iso-latin-1-unix that
char-displayable-p would say only relevant latin1 chars are displayable.
I believe this is how it was in emacs24 was (and which helped avoid a
lot of very unattractive \ display escaping, at least from code knowing
not to try to display the undisplayable).
In GNU Emacs 25.1.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2017-01-01, modified by Debian built on x86-csail-01
Important settings:
value of $LANG: en_AU.iso88591
locale-coding-system: iso-latin-1-unix
next reply other threads:[~2017-04-08 2:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 2:20 Kevin Ryde [this message]
2017-04-08 7:42 ` bug#26396: 25.1; char-displayable-p on a latin1 tty 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efx31vxy.fsf@blah.blah \
--to=user42_kevin@yahoo.com.au \
--cc=26396@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.