From: Eli Zaretskii <eliz@gnu.org>
To: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: tabulated-list-init-header and glyphless-char-display
Date: Fri, 08 Apr 2011 21:59:32 +0300 [thread overview]
Message-ID: <83ipuotvqj.fsf@gnu.org> (raw)
In-Reply-To: <83k4f4twam.fsf@gnu.org>
> Date: Fri, 08 Apr 2011 21:47:29 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
>
> > From: Chong Yidong <cyd@stupidchicken.com>
> > Cc: emacs-devel@gnu.org
> > Date: Fri, 08 Apr 2011 14:27:37 -0400
> >
> > We can probably use "^" and "v" when the unicode glyphs cannot be
> > displayed, but it sure would be nice to the glyphs whereever possible.
> > Any idea how to go about checking this?
>
> I think you will find glyphless-char-display (which is a char-table)
> useful.
Also this:
(unencodable-char-position 0 1
(terminal-coding-system)
nil (string CHARACTER))
will tell you whether CHARACTER can be safely encoded for the selected
frame's terminal.
next prev parent reply other threads:[~2011-04-08 18:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 17:17 tabulated-list-init-header and glyphless-char-display Eli Zaretskii
2011-04-08 18:27 ` Chong Yidong
2011-04-08 18:47 ` Eli Zaretskii
2011-04-08 18:59 ` Eli Zaretskii [this message]
2011-04-09 19:26 ` Chong Yidong
2011-04-10 3:59 ` Stefan Monnier
2011-04-10 5:24 ` Eli Zaretskii
2011-04-10 15:47 ` Chong Yidong
2011-04-10 16:53 ` Eli Zaretskii
2011-04-10 18:11 ` Chong Yidong
2011-04-11 17:03 ` Eli Zaretskii
2011-04-11 17:31 ` Chong Yidong
2011-04-11 18:04 ` Eli Zaretskii
2011-04-11 18:39 ` Chong Yidong
2011-04-11 19:27 ` Eli Zaretskii
2011-04-11 22:31 ` Chong Yidong
2011-04-12 3:57 ` Stefan Monnier
2011-04-12 4:51 ` Eli Zaretskii
2011-04-12 5:42 ` Kevin Rodgers
2011-04-12 5:58 ` Eli Zaretskii
2011-04-12 16:12 ` Chong Yidong
2011-04-12 16:45 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2011-04-08 17:26 Eli Zaretskii
2011-04-09 10:26 ` Štěpán Němec
2011-04-09 12:12 ` Eli Zaretskii
2011-04-09 13:56 ` Stefan Monnier
2011-04-09 15:37 ` 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=83ipuotvqj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.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).