From: Tassilo Horn <tsdh@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 21729@debbugs.gnu.org
Subject: bug#21729: doc-view messed up by early auto-revert
Date: Thu, 22 Oct 2015 17:11:29 +0200 [thread overview]
Message-ID: <87vb9zx7j2.fsf@gnu.org> (raw)
In-Reply-To: <jwvy4evvyxy.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Thu, 22 Oct 2015 09:10:14 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> Hm, no, that won't work. I currently work on some large document
>> (~450 pages). When I compile that, the file changes several times
>> per second during the compilation, then it doesn't change for ~15
>> seconds while latex (lualatex in this case) is still running, and
>> then starts changing again for maybe 3 seconds.
>
> So we could additionally either check that the file is valid, or
> simply "fail gracefully" if it isn't (e.g. keep displaying the old
> image, and emit a message pointing to C-c C-c to see the raw data).
> But it's not a deal breaker: in your case, we may end up trying to
> revert the file too early, which is annoying, but as long as we do end
> up re-reverting it when the file is finally complete, I think it's OK.
In commit 11d1422, I've added a check which omits reverting when the PDF
is corrupted and spits out a message if doc-view-revert-buffer has been
called interactively. Seems to work fine but it is annoying that
autorevert.el spits out a "Reverting buffer ..." message whenever it
calls revert-buffer.
I think in doc-view-mode it's obvious enough when a file is being
reverted, so maybe we should set auto-revert-verbose to nil
buffer-locally?
Bye,
Tassilo
next prev parent reply other threads:[~2015-10-22 15:11 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb9zx7j2.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=21729@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.