From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [emacs-bidi] Treatment of LRE,RLE,LRO,RLO,PDF,LRM,RLM
Date: Mon, 29 Nov 2010 15:35:04 +0900 [thread overview]
Message-ID: <tl7lj4cr61z.fsf@m17n.org> (raw)
In-Reply-To: <83wrnz5fac.fsf@gnu.org> (message from Eli Zaretskii on Sat, 27 Nov 2010 10:42:03 +0200)
In article <83wrnz5fac.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> > But, as I wrote before, I'm still hesitating over which is
> > better; keeping glyphless-char-display separate from display
> > table, or integrating that functionality to display table.
> What are the pros and cons, which make you hesitate?
Both glyphless-char-display and display table control the
displaying of each character. I think such a control should
be done by a single mechanism. At least it will benefit
users in a long run.
But, the biggest concern is about the backward
compatibility. Currently, a display table element is nil or
vector of characters. If there's a code that assumes that a
non-nil element is a vector of characters, it will be
broken. Next, a display table is not inherited. So, if
buffer-display-table or a window-specific display is set,
standard-display-table is not looked up. At last, there are
several standard-display-XXX functions
(e.g. standard-display-8bit). At the moment, I don't know
how to make the functionality of
glyphless-char-display-control go with them.
> > I agree on exempting TAB and NL from c0-control group.
> Done.
Thank you.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2010-11-29 6:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tl7hbis1xop.fsf@m17n.org>
[not found] ` <AANLkTinrGPzGquxPmfigvZLzGbids39yU942sfwKGMYk@mail.gmail.com>
2010-08-19 2:49 ` [emacs-bidi] Treatment of LRE,RLE,LRO,RLO,PDF,LRM,RLM Kenichi Handa
2010-11-01 8:15 ` Kenichi Handa
2010-11-01 9:57 ` Eli Zaretskii
2010-11-01 11:16 ` Kenichi Handa
2010-11-13 13:51 ` [emacs-bidi] " Eli Zaretskii
2010-11-17 5:58 ` Kenichi Handa
2010-11-17 7:14 ` Kenichi Handa
2010-11-17 12:21 ` Eli Zaretskii
2010-11-17 19:20 ` Eli Zaretskii
2010-11-13 13:44 ` Eli Zaretskii
2010-11-13 14:07 ` Eli Zaretskii
2010-11-17 3:57 ` Kenichi Handa
2010-11-17 12:26 ` Eli Zaretskii
2010-11-17 12:55 ` Andreas Schwab
2010-11-17 13:24 ` Stefan Monnier
2010-11-18 20:07 ` Eli Zaretskii
2010-11-17 17:54 ` Eli Zaretskii
2010-11-17 23:59 ` Stefan Monnier
2010-11-18 20:04 ` Eli Zaretskii
2010-11-18 22:15 ` Stefan Monnier
2010-11-19 11:31 ` Eli Zaretskii
2010-11-20 15:06 ` Eli Zaretskii
2010-11-19 9:53 ` Andreas Schwab
2010-11-19 11:31 ` Eli Zaretskii
2010-11-19 11:47 ` Andreas Schwab
2010-11-17 19:39 ` Eli Zaretskii
2010-11-26 12:20 ` Eli Zaretskii
2010-11-26 12:29 ` Kenichi Handa
2010-11-27 8:42 ` Eli Zaretskii
2010-11-29 6:35 ` Kenichi Handa [this message]
2010-11-29 18:06 ` Stefan Monnier
2010-11-20 14:38 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tl7lj4cr61z.fsf@m17n.org \
--to=handa@m17n.org \
--cc=eliz@gnu.org \
--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 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.