From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: paul.r.ml@gmail.com, rms@gnu.org, joakim@verona.se, emacs-devel@gnu.org
Subject: Re: Dired auto-revert
Date: Wed, 23 Sep 2009 12:05:14 +0300 [thread overview]
Message-ID: <87ab0m2dnt.fsf@mail.jurta.org> (raw)
In-Reply-To: <CADA78E13B094417BB787E4216E6F185@us.oracle.com> (Drew Adams's message of "Mon, 21 Sep 2009 15:29:30 -0700")
>> Or maybe we should add a new option that defines whether revert
>> automatically or just display a message.
>
> Yes, please, if we implement the possibility of auto-reverting, then let's keep
> it only a possibility, not an obligation. IOW, let's also make it possible to
> choose not to auto-revert.
>
> It might even be useful to give such control for specific directories or classes
> of directories: have two options, analogous to `special-display-buffer-names'
> and `special-display-regexps' (and `same-window-*').
>
> `dired-auto-revert-names':
> List of directories for which Dired auto-reverts.
>
> `dired-auto-revert-regexps':
> List of regexps specifying which Dired buffers are auto-reverted.
>
> If both are nil, then there is no auto-reverting.
> If `dired-auto-revert-regexps' is `(".")', then all Dired buffers are
> auto-reverted.
I thought just an option for remote files would be enough. Maybe it could
be implemented as a regexp but better as a predicate for defcustom that
tests `file-remote-p' and also could test the directory size, subdirectories
presence in the same dired buffer, etc.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-09-23 9:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 20:34 Emacs inotify support? joakim
2009-09-11 21:28 ` Lennart Borgman
2009-09-11 22:54 ` Antoine Levitt
2009-09-11 23:00 ` Lennart Borgman
2009-09-12 13:32 ` Eli Zaretskii
2009-09-12 16:36 ` Antoine Levitt
2009-09-12 16:55 ` Eli Zaretskii
2009-09-12 17:26 ` Antoine Levitt
2009-09-12 19:45 ` Eli Zaretskii
2009-09-12 20:04 ` Antoine Levitt
2009-09-12 21:24 ` Giuseppe Scrivano
2009-09-13 16:39 ` Richard Stallman
2009-09-13 17:28 ` joakim
2009-09-13 19:42 ` Eli Zaretskii
2009-09-13 22:28 ` Lennart Borgman
2009-09-14 5:47 ` joakim
2009-09-14 18:08 ` Eli Zaretskii
2009-09-12 16:46 ` Richard Stallman
2009-09-13 2:27 ` Miles Bader
2009-09-13 9:33 ` David Kastrup
2009-09-12 16:46 ` Richard Stallman
2009-09-14 7:39 ` Paul R
2009-09-15 7:17 ` Richard Stallman
2009-09-17 15:12 ` Juri Linkov
2009-09-18 9:49 ` Richard Stallman
2009-09-18 12:10 ` David Kastrup
2009-09-18 17:14 ` Stefan Monnier
2009-09-18 18:38 ` joakim
2009-09-21 21:45 ` Dired auto-revert (was: Emacs inotify support?) Juri Linkov
2009-09-21 22:29 ` Drew Adams
2009-09-23 9:05 ` Juri Linkov [this message]
2009-12-04 0:11 ` Proced revert (Re: Dired auto-revert) Juri Linkov
2009-12-04 2:17 ` Stefan Monnier
2009-12-04 22:21 ` Roland Winkler
2009-12-04 0:09 ` Dired auto-revert Juri Linkov
2009-12-04 2:15 ` 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=87ab0m2dnt.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=paul.r.ml@gmail.com \
--cc=rms@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 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).