From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: dired.el
Date: Wed, 9 Jun 2004 09:27:57 -0500 (CDT) [thread overview]
Message-ID: <200406091427.i59ERvx08279@raven.dms.auburn.edu> (raw)
In-Reply-To: <jwvise1hx9d.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on 09 Jun 2004 05:59:02 -0400)
Stefan Monnier wrote:
We seem to miscommunicate: most let-bindings of buffer-read-only (99.9% of
which are to nil) are due to people not knowing that they should bind
inhibit-read-only to t instead.
Sorry, I somehow failed to notice that you were talking about a
different variable. I was still thinking about buffer-read-only, even
though I might have written inhibit-read-only.
dired.el and dired-aux.el bind buffer-read-only to nil countless
times, but there is only one single inhibit-read-only binding in the
two files combined. I have the impression that this is not a result
of "not knowing", but rather a result of the fact that the code is
old, probably from before inhibit-read-only existed.
Prolonged bindings of {buffer,inhibit}-read-only both have their own
dangers. For buffer-read-only it is inappropriate mode line updates,
for inhibit-read-only it is the fact that it applies to all buffers,
including the minibuffer (unless one goes through the trouble of
making a buffer-local binding). So one can not just blindly replace
either one by the other.
In the case of undo, I actually believe that _both_ are safe.
Sincerely,
Luc.
next prev parent reply other threads:[~2004-06-09 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 19:26 dired.el Luc Teirlinck
2004-06-06 19:40 ` dired.el Luc Teirlinck
2004-06-06 20:19 ` dired.el David Kastrup
2004-06-07 9:04 ` dired.el Stefan Monnier
2004-06-07 16:34 ` dired.el Luc Teirlinck
2004-06-09 9:59 ` dired.el Stefan Monnier
2004-06-09 14:27 ` Luc Teirlinck [this message]
2004-06-07 7:10 ` dired.el Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2004-06-03 3:43 dired.el Luc Teirlinck
2004-06-03 5:09 ` dired.el Luc Teirlinck
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=200406091427.i59ERvx08279@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
/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.