unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: 68318-done@debbugs.gnu.org, winkler@gnu.org, 74308@debbugs.gnu.org
Subject: bug#74308: 30.0.92; emacs-lisp font-locking word regexp
Date: Sun, 17 Nov 2024 08:22:23 +0200	[thread overview]
Message-ID: <86o72ewfa8.fsf@gnu.org> (raw)
In-Reply-To: <m25xomhni4.fsf@macmutant.fritz.box> (message from Arash Esbati on Sat, 16 Nov 2024 22:33:55 +0100)

> From: Arash Esbati <arash@gnu.org>
> Cc: Roland Winkler <winkler@gnu.org>,  74308@debbugs.gnu.org
> Date: Sat, 16 Nov 2024 22:33:55 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > merge 74308 74307
> > thanks
> >
> >> From: Roland Winkler <winkler@gnu.org>
> >> Date: Mon, 11 Nov 2024 00:30:46 -0600
> >> 
> >> Starting from emacs -Q, put the following into a buffer with
> >> emacs-lisp-mode
> >> 
> >>   (setq foo "\\<foo\\>")
> >> 
> >> The part "foo\\" of the string "\\<foo\\>" will get
> >> font-lock-variable-name-face, which looks odd.
> >> 
> >> I believe, this is due to a clause in lisp-mode.el that says
> >> 
> >>          ;; Words inside \\[], \\<>, \\{} or \\`' tend to be for
> >>          ;; `substitute-command-keys'.
> >> 
> >> But this assumption is not always correct, in particular if ">" is
> >> preceded by "\\", which happens when constructing regexps.
> >
> > This is an exact duplicate of bug#74307 that you submitted just 2
> > minutes earlier, so I'm merging them.
> 
> I think bug#68318 is also about the same issue; it can be merged into
> this one as well.

Thanks.  Since this bug was already closed, I'm therefore closing
bug#68318 as well.





      reply	other threads:[~2024-11-17  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11  6:30 bug#74308: 30.0.92; emacs-lisp font-locking word regexp Roland Winkler
2024-11-11 12:30 ` Eli Zaretskii
2024-11-16 21:33   ` Arash Esbati
2024-11-17  6:22     ` Eli Zaretskii [this message]

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=86o72ewfa8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=68318-done@debbugs.gnu.org \
    --cc=74308@debbugs.gnu.org \
    --cc=arash@gnu.org \
    --cc=winkler@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 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).