all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mjh@mjhoy.com, 67569-done@debbugs.gnu.org
Subject: bug#67569: 29.1; ruby-mode syntax highlighting breaks with variable named "index" and "/" operator
Date: Sat, 9 Dec 2023 20:00:27 +0200	[thread overview]
Message-ID: <bc411f31-f36e-06f8-69c7-63384a7202e0@gutov.dev> (raw)
In-Reply-To: <83plzfw9m9.fsf@gnu.org>

On 09/12/2023 19:47, Eli Zaretskii wrote:
>> Date: Sat, 9 Dec 2023 19:38:28 +0200
>> Cc:mjh@mjhoy.com,67569@debbugs.gnu.org
>> From: Dmitry Gutov<dmitry@gutov.dev>
>>
>>>> Eli, should we put this in Emacs 29.2? It's not a regression (a fairly
>>>> old problem), but the fix looks simple enough.
>>> Yes, please.
>> Very good, pushed to emacs-29.
>>
>> Here's a second patch on top which gets rid of the whitelist altogether
>> (the new heuristic seems to cover the cases better anyway), though I'm
>> on the fence whether this should go here or into master.
>>
>> It seems to work well with some testing, but it is more adventurous than
>> the previous one.
> Yes, I think we have enough adventures on emacs-29.

All right. Guess I'm closing this, then, and will push the second patch 
after the next merge into master.





      reply	other threads:[~2023-12-09 18:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 14:27 bug#67569: 29.1; ruby-mode syntax highlighting breaks with variable named "index" and "/" operator Michael Hoy
2023-12-09  8:32 ` Eli Zaretskii
2023-12-16 11:58   ` Eli Zaretskii
2023-12-16 12:17     ` Dmitry Gutov
2023-12-09 14:13 ` Dmitry Gutov
2023-12-09 14:35   ` Eli Zaretskii
2023-12-09 17:38     ` Dmitry Gutov
2023-12-09 17:47       ` Eli Zaretskii
2023-12-09 18:00         ` Dmitry Gutov [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bc411f31-f36e-06f8-69c7-63384a7202e0@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=67569-done@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mjh@mjhoy.com \
    /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.