From: Tassilo Horn <tsdh@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 21729@debbugs.gnu.org,
Nicolas Richard <youngfrog@members.fsf.org>,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#21729: doc-view messed up by early auto-revert
Date: Thu, 03 Oct 2019 11:21:29 +0200 [thread overview]
Message-ID: <87h84q9obq.fsf@gnu.org> (raw)
In-Reply-To: <87muenl0fl.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 29 Sep 2019 15:03:10 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> It seems the original issue reported here was fixed, but then an
> enhancement request is discussed:
>
> Tassilo Horn <tsdh@gnu.org> writes:
>
>> Alternatively, we could of course enhance autorevert.el, e.g., by
>> introducing some buffer-local variable `auto-revert-predicate' which is
>> run by auto-revert in order to test if the current buffer can be
>> reverted right now. That could then be used by doc-view, and I guess
>> there are other modes which could make use of such a feature, too.
>>
>> Stefan, do you think that would be a good idea?
>
> I'm not Stefan, but I think that sounds like a good idea.
I don't know. There are not many file types which are regenerated
(where regeneration modifies the file several times and takes some
time), likely to be opened in Emacs, and which can be checked for
validity.
Bye,
Tassilo
next prev parent reply other threads:[~2019-10-03 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 18:05 bug#21729: doc-view messed up by early auto-revert Stefan Monnier
2015-10-22 6:22 ` Tassilo Horn
2015-10-22 13:10 ` Stefan Monnier
2015-10-22 15:11 ` Tassilo Horn
2015-10-23 9:33 ` Nicolas Richard
2015-10-23 10:08 ` Tassilo Horn
2019-09-29 13:03 ` Lars Ingebrigtsen
2019-10-03 9:21 ` Tassilo Horn [this message]
2022-02-03 21:01 ` Lars Ingebrigtsen
2019-10-03 13:31 ` Stefan Monnier
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=87h84q9obq.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=21729@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=youngfrog@members.fsf.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 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).