From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: Richard Stallman <rms@gnu.org>,
ulrich@a0.complang.tuwien.ac.at, emacs-devel@gnu.org
Subject: Re: Latin-1 non breaking space not highlighted
Date: Thu, 18 Apr 2002 06:18:19 -0400 [thread overview]
Message-ID: <200204181018.g3IAIJX00462@rum.cs.yale.edu> (raw)
In-Reply-To: Pine.SUN.3.91.1020418083751.2931A-100000@is
>
> On Mon, 15 Apr 2002, Richard Stallman wrote:
>
> > I see two possible solutions:
> >
> > - hardcode a few more special characters, like ISO8859-x NBSP and a
> > few Unicode characters;
> >
> > For now, I think we should do it that way.
>
> Perhaps the char-table implementation suggested by Handa-san is better.
> It is certainly easier to customize by users, so it's more flexible.
I think using fundamental-mode's syntax-table (i.e. the standard syntax-table)
is the best choice.
Stefan
next prev parent reply other threads:[~2002-04-18 10:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-07 23:31 Latin-1 non breaking space not highlighted Ulrich Neumerkel
2002-04-08 7:08 ` Eli Zaretskii
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 [this message]
2002-04-18 11:33 ` Eli Zaretskii
2002-04-18 10:36 ` Stefan Monnier
2002-04-19 5:25 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-04-14 23:30 Ulrich Neumerkel
2002-04-16 20:16 ` Richard Stallman
2002-04-14 23:54 Kenichi Handa
2002-04-19 1:55 Kenichi Handa
2002-04-19 13:55 ` Stefan Monnier
2002-04-19 14:07 ` Miles Bader
2002-04-22 1:53 Kenichi Handa
2002-04-22 22:37 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200204181018.g3IAIJX00462@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--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 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.