From: "Antoine Levitt" <smeuuh@gmail.com>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: [Patch] Behavior of dired when there already is a dired buffer of the same directory
Date: Mon, 1 Sep 2008 03:26:36 +0200 [thread overview]
Message-ID: <6fa54e4e0808311826w4222b2bbk1e934b76631f99dd@mail.gmail.com> (raw)
In-Reply-To: <48BB413E.8010107@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 628 bytes --]
That only checks for tramp/similar file handling. I don't think we can check
for the underlying file system in an OS-independent fashion (gvfs, mounts
... are all ways of making remote files look like regular files). Maybe a
solution would be to provide an option to automatically refresh, with a
regexp list of files to ignore ? (which could be set to e.g.
("^/media/cdrom", ".gvfs"))
2008/9/1 Lennart Borgman (gmail) <lennart.borgman@gmail.com>
> Antoine Levitt wrote:
> > anyway). Is there a reliable way to know if accessing a file is fast and
> > side-effects free ? If there is, dired could hook to
>
>
> file-remote-p
>
[-- Attachment #2: Type: text/html, Size: 978 bytes --]
next prev parent reply other threads:[~2008-09-01 1:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 22:50 [Patch] Behavior of dired when there already is a dired buffer of the same directory Antoine Levitt
2008-08-31 23:02 ` Lennart Borgman (gmail)
2008-09-01 17:47 ` Mathias Dahl
2008-09-01 18:00 ` David House
2008-09-01 0:36 ` Miles Bader
2008-09-01 0:53 ` Antoine Levitt
2008-09-01 1:11 ` Lennart Borgman (gmail)
2008-09-01 1:26 ` Antoine Levitt [this message]
2008-09-01 2:47 ` Miles Bader
2008-09-01 3:06 ` Stefan Monnier
2008-09-01 7:25 ` Lennart Borgman (gmail)
2008-09-02 1:08 ` Richard M. Stallman
2008-09-02 14:00 ` Antoine Levitt
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=6fa54e4e0808311826w4222b2bbk1e934b76631f99dd@mail.gmail.com \
--to=smeuuh@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=miles@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).