From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: non-breaking hyphens
Date: Tue, 18 Oct 2011 09:41:16 -0400 [thread overview]
Message-ID: <E1RG9uu-0007B6-O0@fencepost.gnu.org> (raw)
In-Reply-To: <87pqhuwli7.fsf@gnu.org> (message from Chong Yidong on Tue, 18 Oct 2011 08:08:00 -0400)
> From: Chong Yidong <cyd@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Tue, 18 Oct 2011 08:08:00 -0400
>
> This is what I found, though it does not explain the rationale for the
> feature:
>
> http://lists.gnu.org/archive/html/emacs-devel/2004-12/msg00954.html
> http://lists.gnu.org/archive/html/emacs-devel/2005-01/msg00035.html
Thanks.
> The right way to implement this feature, as brought up in the 2004
> thread, would be to specify the affected characters with a char-table
> rather than hardcoding them.
Yes, we should design the display of these special characters as a
single coherent feature. For example, I discovered a few days ago
that we don't display the U+2028 LINE SEPARATOR character as a line
separator. And there are many other similar Unicode characters that
need our consideration.
(I started to elaborate about this, but found out that I already said
that in http://lists.gnu.org/archive/html/emacs-devel/2008-04/msg01504.html).
> But we should probably leave such a change till after 24.1.
Agreed. How about a bug report on this, to avoid forgetting the
issue?
> In the meantime, I think I'll add non-breaking hyphen and hyphen to the
> hardcoded list, while deferring on the various other space characters;
> many of those spaces are defined to have specific widths, so it's not
> clear that changing their appearance to a highlighted space is the right
> thing for Emacs to do.
I agree.
next prev parent reply other threads:[~2011-10-18 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 13:56 non-breaking hyphens Chong Yidong
2011-10-17 14:45 ` Eli Zaretskii
2011-10-18 3:39 ` Chong Yidong
2011-10-18 4:00 ` Eli Zaretskii
2011-10-18 12:08 ` Chong Yidong
2011-10-18 13:11 ` Stefan Monnier
2011-10-18 17:43 ` Drew Adams
2011-10-19 8:28 ` Juri Linkov
2011-10-19 13:59 ` Drew Adams
2011-10-19 14:37 ` Stefan Monnier
2011-10-18 13:41 ` Eli Zaretskii [this message]
2011-10-19 8:27 ` Juri Linkov
2011-10-19 8:39 ` Eli Zaretskii
2011-10-19 13:59 ` Drew Adams
2011-10-19 15:12 ` 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=E1RG9uu-0007B6-O0@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=cyd@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.