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: one.last.kiss@outlook.com, 64281-done@debbugs.gnu.org
Subject: bug#64281: [Feature Request] Recognize “#” syntax
Date: Mon, 26 Jun 2023 15:21:36 +0300	[thread overview]
Message-ID: <83wmzqwh0v.fsf@gnu.org> (raw)
In-Reply-To: <jwv1qhzo8bl.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 25 Jun 2023 11:46:13 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Shynur Xie <one.last.kiss@outlook.com>,  64281@debbugs.gnu.org
> Date: Sun, 25 Jun 2023 11:46:13 -0400
> 
> >> It seems that this is a intentional behavior:
> >>
> >> <https://www.gnu.org/software/emacs/manual/html_node/elisp/File-Local-Variables.html>:
> >>
> >> > For additional safety, read-circle is temporarily bound to nil when
> >> > Emacs reads file-local variables.
> >>
> >> No further question; can be closed now.
> >>
> >> (I wonder if we can treat ~/.emacs.d/.dir-locals.el specially, or tell
> >>  Emacs which files can be treated specially -- enable read-circle.)
> >
> > Stefan, any comments before we close this?
> 
> file/dir-local variables are dangerous enough as it is, I think.  If you
> want to do better, you can use an actual ELisp file.

Agreed.





      parent reply	other threads:[~2023-06-26 12:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25 11:54 bug#64281: [Feature Request] Recognize “#” syntax when reading local-variables Shynur Xie
2023-06-25 13:53 ` bug#64281: [Feature Request] Recognize “#” syntax Shynur Xie
2023-06-25 15:08   ` Eli Zaretskii
2023-06-25 15:46     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-25 16:16       ` Drew Adams
2023-06-26 10:21         ` Shynur Xie
2023-06-26 12:21       ` 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=83wmzqwh0v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64281-done@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=one.last.kiss@outlook.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).