From: Chong Yidong <cyd@stupidchicken.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: tabulated-list-init-header and glyphless-char-display
Date: Mon, 11 Apr 2011 14:39:15 -0400 [thread overview]
Message-ID: <87vcykaazw.fsf@stupidchicken.com> (raw)
In-Reply-To: <83oc4cr7fe.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 Apr 2011 21:04:21 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> > No, I was trying to suggest something much simpler: see if these
>> > characters can be displayed, e.g. with unencodable-char-position (and
>> > something similar for GUI sessions), and if so, use surrogates
>> > directly in the code, without going through glyphless-char-display.
>>
>> How would this handle the multi-tty case?
>
> The only thing that matters on a tty is its encoding, which you pass
> to unencodable-char-position.
>
> If you mean that some frames can be GUI frames, then you can always
> know what kind of frame is the selected one, right?
>
> Or are you thinking about something else?
Suppose we make the *Process List* buffer and display it in a GUI
terminal. Then, we create a text terminal in the same Emacs session,
and display that same buffer in the text terminal.
The buffer has to display correctly, without a priori knowledge of the
terminal(s) on which it is to be displayed.
Therefore, checking unencodable-char-position at buffer creation time
does not work. The fallback behavior has to be done at redisplay time.
next prev parent reply other threads:[~2011-04-11 18:39 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
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 [this message]
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=87vcykaazw.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).