From: Luc Teirlinck <teirllm@dms.auburn.edu>
Subject: find-file-not-found-functions
Date: Tue, 25 May 2004 15:58:35 -0500 (CDT) [thread overview]
Message-ID: <200405252058.i4PKwZH25711@raven.dms.auburn.edu> (raw)
A little while ago, I made a change to find-file-noselect-1 that
limited the scope of the `inhibit-read-only' binding in such a way
that `inhibit-read-only' became nil during the execution of
`find-file-not-found-functions' and `find-file-hook'. Before, it was
bound to t. The reason for the change was that the t binding was not
documented and that, in the case of `find-file-hook', it caused a bug.
As a side effect of fixing a bug in my previous change,
`inhibit-read-only' is back to t during the execution of
`find-file-not-found-functions'. I now believe that, while my
previous change made sense for `find-file-hook', it might have been a
bad idea for `find-file-not-found-functions'. I have the impression
that PC-look-for-include-file and maybe other functions rely on
inhibit-read-only being t.
What about just _documenting_ the fact that `inhibit-read-only' is t
during the execution of `find-file-not-found-functions'? I could do
this, if desired (docstring and Elisp manual).
Sincerely,
Luc.
next reply other threads:[~2004-05-25 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 20:58 Luc Teirlinck [this message]
2004-05-27 12:46 ` find-file-not-found-functions Richard Stallman
2004-05-27 22:08 ` find-file-not-found-functions Luc Teirlinck
2004-05-29 1:44 ` find-file-not-found-functions Richard Stallman
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=200405252058.i4PKwZH25711@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
/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).