From: Eli Zaretskii <eliz@gnu.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 43412@debbugs.gnu.org
Subject: bug#43412: [FEATURE] autorevert-only-if-visible [PATCH]
Date: Tue, 15 Sep 2020 17:30:31 +0300 [thread overview]
Message-ID: <83y2lb8648.fsf@gnu.org> (raw)
In-Reply-To: <20200915040728.77ufv7g6bekvrzqa@E15-2016.optimum.net> (message from Boruch Baum on Tue, 15 Sep 2020 00:07:28 -0400)
> Date: Tue, 15 Sep 2020 00:07:28 -0400
> From: Boruch Baum <boruch_baum@gmx.com>
>
> +(defcustom auto-revert-only-if-visible nil
> + "If non-nil, suppress Auto-Revert Mode when a buffer isn't visible."
"Visible" is ambiguous in this context. I suggest "not displayed in
any window" instead. Or, better, just "auto-revert only if buffer is
displayed" (which also solved a problem with double negation).
> + :version "28")
^^^^
"28.1"
> + (if (display-graphic-p) 'visible (window-normalize-frame nil)))))))
Is the different treatment of GUI and TTY frames necessary here?
Btw, what will be the effect of this option? Suppose some buffer was
not displayed and missed its auto-revert opportunity. Then I switch
to it in some window -- will it appear with stale contents, or will it
auto-revert before being displayed in the window?
next prev parent reply other threads:[~2020-09-15 14:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 4:07 bug#43412: [FEATURE] autorevert-only-if-visible [PATCH] Boruch Baum
2020-09-15 14:30 ` Eli Zaretskii [this message]
2020-09-15 15:39 ` Boruch Baum
2020-09-15 15:49 ` Eli Zaretskii
2020-09-15 16:12 ` Boruch Baum
2020-09-15 17:24 ` Eli Zaretskii
2020-09-16 20:11 ` Boruch Baum
2020-09-17 13:13 ` Eli Zaretskii
2020-09-17 20:10 ` Boruch Baum
2020-09-18 6:35 ` Eli Zaretskii
2020-09-18 7:49 ` martin rudalics
2020-09-29 13:05 ` Boruch Baum
2020-09-29 14:34 ` martin rudalics
2020-09-29 14:45 ` Eli Zaretskii
2020-09-15 18:47 ` Michael Albinus
2020-09-15 19:31 ` Boruch Baum
2020-09-17 11:07 ` Michael Albinus
2020-09-17 20:03 ` Boruch Baum
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=83y2lb8648.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43412@debbugs.gnu.org \
--cc=boruch_baum@gmx.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).