unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mjh@mjhoy.com, 67569@debbugs.gnu.org
Subject: bug#67569: 29.1; ruby-mode syntax highlighting breaks with variable named "index" and "/" operator
Date: Sat, 16 Dec 2023 14:17:36 +0200	[thread overview]
Message-ID: <58e3e731-099a-41a4-4c36-9da7ed093c18@gutov.dev> (raw)
In-Reply-To: <83sf42mka6.fsf@gnu.org>

This is resolved and closed, I just replied to a different subthread.

I suppose you set up some automation for pinging non-respondents? :)

On 16/12/2023 13:58, Eli Zaretskii wrote:
> Ping!
> 
>> Cc:67569@debbugs.gnu.org
>> Date: Sat, 09 Dec 2023 10:32:22 +0200
>> From: Eli Zaretskii<eliz@gnu.org>
>>
>>> From: Michael Hoy<mjh@mjhoy.com>
>>> Date: Fri, 01 Dec 2023 09:27:47 -0500
>>>
>>> In the standard ruby-mode, a variable named "index" followed by a "/"
>>> causes the syntax highlighting to break -- it appears that after the
>>> slash everything is interpreted as part of a regular expression until
>>> another "/" appears.
>>>
>>> You can reproduce this fairly easily. using 'emacs -Q', go to the
>>> scratch buffer and clear it. Run 'M-x ruby-mode'. Enter something like
>>> the following:
>>>
>>> def foo
>>>    index = 5
>>>    x = index / 3
>>>    puts "#{x}"
>>> end
>>>
>>> Note that starting after the "/" until the end, syntax highlighting and
>>> indentation break (everything, in my color scheme, is purple). If you
>>> add a "/" for instance to the "puts" line, syntax highlighting and
>>> indentation will be restored after that.
>>>
>>> There is a report here about the bug:
>>> https://emacs.stackexchange.com/questions/23802/division-sometimes-breaks-syntax-highlighting-in-ruby-mode
>>> The author says in the comments they used "M-x report-emacs-bug", but I
>>> couldn't find it (and the comments suggest that it may not have been
>>> sent correctly). Apologies if this is already reported!
>> Dmitry, any comments?
>>
>>
>>
>>






  reply	other threads:[~2023-12-16 12:17 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 [this message]
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

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=58e3e731-099a-41a4-4c36-9da7ed093c18@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=67569@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 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).