From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: martin rudalics <rudalics@gmx.at>, emacs-devel@gnu.org
Subject: Re: regexp font-lock highlighting
Date: Wed, 08 Jun 2005 18:42:23 -0400 [thread overview]
Message-ID: <87u0k8eaov.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87wtp461xu.fsf@jurta.org> (Juri Linkov's message of "Wed, 08 Jun 2005 23:34:38 +0300")
>> I tried to implement variants of that but it did not turn out well.
>> Highlighting backslashes only is more distracting than useful. Having
>> `<' or `w' stand out with bold face makes groupings much less readable.
> A different face could be used for `<', `w' and other constructs.
I can't help wondering what would be the benefit of highlighting things like
\< and \w. Highlighting \( and \| and \) can make sense since it helps
doing visual paren matching (tho I find blink-matching-open to work fairly
well in most cases, I can see that it sometimes gets confused and also it
currently doesn't understand the concept of the "matching open of an infix
operator").
Please leave \< and \w alone, thank you.
Stefan
next prev parent reply other threads:[~2005-06-08 22:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 8:41 regexp font-lock highlighting martin rudalics
2005-05-31 2:45 ` Daniel Brockman
2005-06-01 9:39 ` Richard Stallman
2005-06-04 8:11 ` martin rudalics
2005-06-04 17:59 ` Richard Stallman
2005-06-06 9:33 ` martin rudalics
2005-06-11 23:17 ` Richard Stallman
2005-06-15 16:00 ` martin rudalics
2005-07-03 0:09 ` Juri Linkov
2005-07-03 4:10 ` Luc Teirlinck
2005-07-03 6:03 ` Eli Zaretskii
2005-07-03 9:10 ` martin rudalics
2005-07-04 0:09 ` Miles Bader
2005-06-06 13:05 ` Juri Linkov
2005-06-08 15:13 ` martin rudalics
2005-06-08 20:34 ` Juri Linkov
2005-06-08 22:42 ` Stefan Monnier [this message]
2005-06-08 23:32 ` Juri Linkov
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=87u0k8eaov.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.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).