unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: tabulated-list-init-header and glyphless-char-display
Date: Sat, 09 Apr 2011 15:12:09 +0300	[thread overview]
Message-ID: <83aafztyhy.fsf@gnu.org> (raw)
In-Reply-To: <87wrj390v1.fsf@gmail.com>

> From: Štěpán Němec <stepnem@gmail.com>
> Cc: Chong Yidong <cyd@stupidchicken.com>,  emacs-devel@gnu.org
> Date: Sat, 09 Apr 2011 12:26:42 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > tabulated-list-init-header assumes without testing that u+25b2 and
> > u+25bc will be displayed as themselves.  But with various values of
> > glyphless-char-display-control, this may not be true.  Also, on text
> > terminals these characters generally cannot be displayed, which makes
>                              ^^^^^^^^^
> I wonder what your meant by this word?

"Generally" as in "for any terminal encoding but one".

> Both characters display fine for me in urxvt and xterm, and even in
> the linux console (displayed as up/down arrows instead of triangles)
> on a Debian system. Just a data point.

That's exactly the _only_ terminal encoding where these characters can
be displayed correctly, and even then assuming that the terminal can
display them.  Displaying them as an up and down arrow is just an
emulation (and not a faithful one at that, in this case, if you ask
me).




  reply	other threads:[~2011-04-09 12:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 17:26 tabulated-list-init-header and glyphless-char-display Eli Zaretskii
2011-04-09 10:26 ` Štěpán Němec
2011-04-09 12:12   ` Eli Zaretskii [this message]
2011-04-09 13:56     ` Stefan Monnier
2011-04-09 15:37       ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2011-04-08 17:17 Eli Zaretskii
2011-04-08 18:27 ` Chong Yidong
2011-04-08 18:47   ` Eli Zaretskii
2011-04-08 18:59     ` Eli Zaretskii
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

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=83aafztyhy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=stepnem@gmail.com \
    /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).