unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: sigurddam@hotmail.com, 73872@debbugs.gnu.org
Subject: bug#73872: 30.0.91; emacs-lisp-mode-syntax-table active when calling `describe-variable' on variable with textually large value.
Date: Sat, 07 Dec 2024 15:10:53 +0200	[thread overview]
Message-ID: <86ikrviqoy.fsf@gnu.org> (raw)
In-Reply-To: <jwvh67nvuta.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 01 Dec 2024 18:41:23 -0500)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Sun, 01 Dec 2024 18:41:23 -0500
> 
> >> Ping!  Sigurd, could you please answer Stefan's questions?
> > Oh, I am so sorry, Stefan's mail had ended up in my junk folder. I
> > thought we were still waiting for his reply. Thanks for pinging me!
> >> > I'm curious: in which context did you notice this?
> >> > Does it lead to an undesirable behavior in a specific case?
> > I have rainbow-delimiters-mode from the rainbow-delimiters package
> > enabled everywhere, which means that font lock is enabled everywhere.
> > The syntax table of help mode has ?; as a comment starter, so wherever
> > it is used in docstrings, the remainder of that line will be
> > highlighted as a comment in the help buffer. I changed the syntax
> > class of ?; in help-mode-syntax-table, but I noticed that sometimes it
> > would still be interpreted as a comment starter, which led me to
> > finding the bug.
> 
> Aahhhh!
> So the underlying problem already bite in the usual case but you worked
> around it by changing `help-mode-syntax-table`.
> I think your change to `help-mode-syntax-table` is about right, so we
> should include it in any fix to this bug.

I was going to install that change, but then I noticed that it removed
the call to terpri.  Is that intentional?

(And why did we start discussing this in private email, without CC'ing
the bug tracker?  I've now added it; please use Reply All to reply.)





  parent reply	other threads:[~2024-12-07 13:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 22:14 bug#73872: 30.0.91; emacs-lisp-mode-syntax-table active when calling `describe-variable' on variable with textually large value Sigurd Dam Sonniks
2024-11-02 11:55 ` Eli Zaretskii
     [not found]   ` <jwvsertuche.fsf-monnier+emacs@gnu.org>
2024-11-30  9:49     ` Eli Zaretskii
     [not found]       ` <DBAP195MB104976F58C31051E74A4F05CB92B2@DBAP195MB1049.EURP195.PROD.OUTLOOK.COM>
     [not found]         ` <jwvh67nvuta.fsf-monnier+emacs@gnu.org>
2024-12-07 13:10           ` Eli Zaretskii [this message]
2024-12-21  9:12             ` Eli Zaretskii
2024-12-21 15:10             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=86ikrviqoy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=73872@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=sigurddam@hotmail.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).