all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Chong Yidong <cyd@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: non-breaking hyphens
Date: Tue, 18 Oct 2011 09:11:08 -0400	[thread overview]
Message-ID: <jwvlisitptv.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87pqhuwli7.fsf@gnu.org> (Chong Yidong's message of "Tue, 18 Oct 2011 08:08:00 -0400")

>>> I'm not sure I understand the goal of `nobreak-char-display'.  Is it for
>>> warning the user when there is an ASCII look-alike character that isn't
>>> really ASCII?  I guess that's mainly to avoid issues with source code?
>> Yes, probably.  But I'm only guessing here.  Can you find any traces
>> of discussing this in the archives?

I do remember it being the result (through various discussions, as you
can imagine) of bug reports where a NBSP was accidentally inserted in
source code instead of a SPC, which can be difficult to track down.

> 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.  But we should probably leave such a change
> till after 24.1.

I believe the general solution is along the lines of what the GNU ELPA
packae "markchars" does.  The current solution was a simple solution for
the sub-cases that can happen commonly in programming languages.

The reason why it's important to handle programming languages is that
visual similarity is not understood by compilers ;-)
In contrast for text buffers (or even LaTeX and HTML), it's much
less problematic.

Also the significant cases are the ones where the similarity is between
a "plain ASCII" char and some other one.


        Stefan



  reply	other threads:[~2011-10-18 13:11 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 [this message]
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
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=jwvlisitptv.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=cyd@gnu.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.