From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: monnier+gnu/emacs@RUM.cs.yale.edu, eliz@is.elta.co.il,
rms@gnu.org, ulrich@a0.complang.tuwien.ac.at,
emacs-devel@gnu.org
Subject: Re: Latin-1 non breaking space not highlighted
Date: Fri, 19 Apr 2002 09:55:11 -0400 [thread overview]
Message-ID: <200204191355.g3JDtBs09265@rum.cs.yale.edu> (raw)
In-Reply-To: 200204190155.KAA08907@etlken.m17n.org
> "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu> writes:
> >> But Handa-san listed a couple of problems with using the standard syntax
> >> tables.
>
> > I seem to have missed his email.
>
> My point is:
> show-trailing-whitespace should not mean highlighting such
> charactes that have "whitespace" SYNTAX, but should mean
> highlighting sucn characters that have "whitespace" GLYPH.
That's a separate issue. Related to whether or not we should
take the display-table into account.
> Both sets of characters mostly overlap but not necessarily
> be the same.
>
> For instance, even if I set syntax of NBSP to "word
> constitute",
When would you do that and why (considering that we're specifically
talking about the global standard-syntax-table) ?
> show-trailing-whitespace should highlight it.
Really ? I think this very much depends on the answer to the
previous question.
We really just need a table somewhere that tells us what is whitespace
and what isn't. Currently I think there are two such tables, one is
the standard-syntax-table, the other is the ` ' category. Actually,
I [:space:] and [:blank:] are two more, but [:space:] relies on the
buffer-local syntax-table (i.e. not good, although it's not that bad
since it only uses it for non-ASCII chars, IIRC) and [:blank:] only
matches ASCII chars (i.e. not good either).
Stefan
next prev parent reply other threads:[~2002-04-19 13:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 1:55 Latin-1 non breaking space not highlighted Kenichi Handa
2002-04-19 13:55 ` Stefan Monnier [this message]
2002-04-19 14:07 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2002-04-22 1:53 Kenichi Handa
2002-04-22 22:37 ` Richard Stallman
2002-04-14 23:54 Kenichi Handa
2002-04-14 23:30 Ulrich Neumerkel
2002-04-16 20:16 ` Richard Stallman
[not found] <Pine.SUN.3.91.1020408100627.28830A-100000@is>
2002-04-09 12:08 ` Richard Stallman
2002-04-09 14:37 ` Eli Zaretskii
2002-04-10 20:16 ` Richard Stallman
2002-04-11 18:54 ` Eli Zaretskii
2002-04-12 8:18 ` Eli Zaretskii
2002-04-13 19:06 ` Richard Stallman
2002-04-14 4:10 ` Eli Zaretskii
2002-04-15 21:59 ` Richard Stallman
2002-04-18 5:38 ` Eli Zaretskii
2002-04-18 10:18 ` Stefan Monnier
2002-04-18 11:33 ` Eli Zaretskii
2002-04-18 10:36 ` Stefan Monnier
2002-04-19 5:25 ` Richard Stallman
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=200204191355.g3JDtBs09265@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=ulrich@a0.complang.tuwien.ac.at \
/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).