From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: tabulated-list-init-header and glyphless-char-display
Date: Tue, 12 Apr 2011 00:51:34 -0400 [thread overview]
Message-ID: <E1Q9VZe-0001pK-8s@fencepost.gnu.org> (raw)
In-Reply-To: <87lizgto6g.fsf@stupidchicken.com> (message from Chong Yidong on Mon, 11 Apr 2011 18:31:51 -0400)
> From: Chong Yidong <cyd@stupidchicken.com>
> Date: Mon, 11 Apr 2011 18:31:51 -0400
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So we are going to invent a new display feature, just to display 2
> > fancy characters in a specialized mode buffer, and in a way that will
> > support simultaneous display in several different display types?
>
> Yep.
>
> > I'd say it's an overkill. Perhaps we should simply compromise and use
> > ASCII art, or no indication at all.
>
> I suspect there will be other situations where it's convenient to use
> unicode glyphs in Emacs buffers. If we can design a sufficiently
> flexible system, I think this is a good investment.
>
> For example, one could imagine a version of table.el that displays
>
> ┌─┬─┐
> │a│b│
> ├─┼─┤
> │ │ │
> └─┴─┘
>
> on graphical terminals, using the Unicode box-drawing glyphs, and
> displays the equivalent ASCII borders on terminals that don't handle
> Unicode.
Then let's extend glyphless-char-display to provide this information.
That is, for each character, it should provide display information
both for GUI and for text-mode displays. It can do that by providing
an option to have an element of the char-table be a vector of 2
elements, instead of just one value today. Most table entries will
still be symbols like today, but we could have some of them be
vectors, as in this case and in the case of line-drawing characters.
I think this is better than the text property suggestion, because
glyphless-char-display can be set once and by default, whereas with
text properties each Lisp application that needs it will have to do
that manually.
WDYT?
next prev parent reply other threads:[~2011-04-12 4:51 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
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 [this message]
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=E1Q9VZe-0001pK-8s@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--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).