From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Alan Mackenzie <acm@muc.de>, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Optional argument for `file-local-copy'
Date: Sun, 14 Dec 2014 08:46:04 -0500 [thread overview]
Message-ID: <jwvsiginy9i.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <877fxuedjj.fsf@gmx.de> (Michael Albinus's message of "Sun, 14 Dec 2014 11:22:40 +0100")
> file-attributes I'm not sure. One implementation inside Tramp could be
> to install a file notifications handler for the remote file if possible.
> We will be informed then, when the remote file changes, and the local
> file is out-dated.
Right, I guess for a client-side cache, the issue is mostly how to check
the freshness of a file, and it seems difficult to design an API that
can cleanly handle all the various ways we could do that.
So maybe the better option is to do the caching on the handler-side.
But there's no need for any changes to file-local-copy for that.
Stefan
next prev parent reply other threads:[~2014-12-14 13:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 11:29 Optional argument for `file-local-copy' Michael Albinus
2014-11-29 13:03 ` Eli Zaretskii
2014-11-29 14:08 ` Alan Mackenzie
2014-11-29 14:39 ` Eli Zaretskii
2014-11-29 15:33 ` Alan Mackenzie
2014-11-29 16:24 ` Thien-Thi Nguyen
2014-11-30 5:22 ` Stefan Monnier
2014-11-30 11:04 ` Michael Albinus
2014-11-30 14:11 ` Stefan Monnier
2014-11-30 17:24 ` Michael Albinus
2014-12-02 14:18 ` Stefan Monnier
2014-12-02 14:53 ` Michael Albinus
2014-12-02 20:55 ` Stefan Monnier
2014-12-02 21:24 ` Michael Albinus
2014-12-02 22:30 ` Stefan Monnier
2014-12-09 13:32 ` Michael Albinus
2014-12-10 14:15 ` Stefan Monnier
2014-12-11 9:20 ` Michael Albinus
2014-12-11 15:22 ` Stefan Monnier
2014-12-14 10:22 ` Michael Albinus
2014-12-14 13:46 ` Stefan Monnier [this message]
2014-12-14 14:24 ` Michael Albinus
2014-12-14 22:37 ` Stefan Monnier
2014-12-15 7:41 ` Michael Albinus
2014-11-30 10:54 ` Michael Albinus
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=jwvsiginy9i.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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).