From: Lars Ingebrigtsen <larsi@gnus.org>
To: Barry OReilly <gundaetiapo@gmail.com>
Cc: 11412@debbugs.gnu.org, 11549@debbugs.gnu.org
Subject: bug#11412: 24.0.95; auto-revert-mode doesn't revert buffer when file becomes writeable
Date: Fri, 02 Jul 2021 13:17:54 +0200 [thread overview]
Message-ID: <87czs1ufq5.fsf@gnus.org> (raw)
In-Reply-To: <87a6o8943h.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 02 Jun 2021 08:24:02 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> This is apparently a feature added in 2004:
>
> commit 90e118abf2dcc4aca4d7a7642247fa488554351e
> Author: Luc Teirlinck <teirllm@auburn.edu>
> AuthorDate: Fri Sep 3 22:28:10 2004 +0000
>
> ;; Bind buffer-read-only in case user has done C-x C-q, so as
> ;; not to forget that. This gives undesirable results when
> ;; the file's mode changes, but that is less common.
> (let ((buffer-read-only buffer-read-only))
> ...
> (revert-buffer 'ignore-auto 'dont-ask 'preserve-modes))))
>
> So auto-reversion doesn't touch the buffer-readedness in case the user
> has set it manually. So I'm not sure whether we should change this
> behaviour here. Anybody got an opinion?
Nobody had an opinion, and I think this is working as designed, and I'm
closing this bug report. If I misunderstood the issue, please respond
to the debbugs address and we'll reopen.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-07-02 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 23:40 bug#11549: auto-revert doesn't revert file permissions as revert-buffer does Barry OReilly
2021-06-02 6:24 ` bug#11412: 24.0.95; auto-revert-mode doesn't revert buffer when file becomes writeable Lars Ingebrigtsen
2021-07-02 11:17 ` Lars Ingebrigtsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-05 15:23 Eric Hanchrow
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=87czs1ufq5.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=11412@debbugs.gnu.org \
--cc=11549@debbugs.gnu.org \
--cc=gundaetiapo@gmail.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).