all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Lin Sun <sunlin7@hotmail.com>, 55865@debbugs.gnu.org
Subject: bug#55865: [BUG] 28.1.50; Msg "Local variables list is not properly terminated." displayed when opening a file with line `print("Local Variable:")`
Date: Wed, 23 Nov 2022 10:22:12 -0500	[thread overview]
Message-ID: <jwv1qpt8zud.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87a6am6lna.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 09 Jun 2022 14:56:09 +0200")

> I don't think there's anything to fix here -- Emacs makes a guess that
> this is a Local Variable section, but then it turns out that it's not,
> and it says so.
>
> So if you don't want that message, you have to obfuscate the string.

Indeed.  If there's something to fix here it's the relative lack
of information.
E.g. we could include in the message some info about the name of the
file in which we found the `Local Variables:` string (and its position
too, while at it).

We could also try and reduce the occurrence of such false positives
(e.g. by checking for the presence of `End:` or the presence of
the same prefix on the next line), but that would increase the
risk of emitting no message when the users do intend to write a `Local
Variables:` section but make a mistake writing it.


        Stefan






      parent reply	other threads:[~2022-11-23 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 23:02 bug#55865: [BUG] 28.1.50; Msg "Local variables list is not properly terminated." displayed when opening a file with line `print("Local Variable:")` Lin Sun
2022-06-09 12:56 ` Lars Ingebrigtsen
2022-06-09 16:04   ` Lin Sun
2022-11-23 15:22   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=jwv1qpt8zud.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=55865@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=sunlin7@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 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.