From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 49143@debbugs.gnu.org
Subject: bug#49143: 28.0.50; find-file-literally doesn't ignore `mode:`
Date: Sun, 20 Jun 2021 13:54:32 -0400 [thread overview]
Message-ID: <jwvzgvkv2uf.fsf@iro.umontreal.ca> (raw)
Package: Emacs
Version: 28.0.50
Contrary to its documentation, it seems that `find-file-literally`
doesn't ignore file-local `mode:` settings any more, as evidenced by the
following backtrace:
dismal-mode()
hack-one-local-variable(mode dismal)
hack-local-variables-apply()
hack-local-variables(no-mode)
run-mode-hooks()
fundamental-mode()
set-buffer-major-mode(#<buffer normalization.dis>)
set-auto-mode()
normal-mode(t)
after-find-file(nil t)
find-file-noselect-1(#<buffer normalization.dis> "~/tmp/normalization.dis" nil nil "~/tmp/normalization.dis" (1347023 65026))
find-file-noselect("~/tmp/normalization.dis")
I suspect the culprit is
commit 5bedbe6b1d5f4b801abf91b4d023d5c4e66418f0
Author: Lars Ingebrigtsen <larsi@gnus.org>
Date: Mon May 10 12:40:11 2021 +0200
Always heed the `lexical-binding' local variable
* doc/lispref/variables.texi (File Local Variables): Document
`permanently-enabled-local-variables'.
* lisp/files.el (enable-local-variables): Mention the new variable.
(set-auto-mode): Always call `hack-local-variables'.
(hack-local-variables): Factor out the variable gathering into its
own function, and respect the new variable (bug#47843).
(hack-local-variables--find-variables): Factored out from
`hack-local-variables'.
(permanently-enabled-local-variables): New variable.
-- Stefan
next reply other threads:[~2021-06-20 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 17:54 Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-06-21 12:54 ` bug#49143: 28.0.50; find-file-literally doesn't ignore `mode:` Lars Ingebrigtsen
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=jwvzgvkv2uf.fsf@iro.umontreal.ca \
--to=bug-gnu-emacs@gnu.org \
--cc=49143@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.