From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Alan Mackenzie <acm@muc.de>, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Optional argument for `file-local-copy'
Date: Thu, 11 Dec 2014 10:20:30 +0100 [thread overview]
Message-ID: <8761dik0f5.fsf@gmx.de> (raw)
In-Reply-To: <jwvy4qfioir.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 10 Dec 2014 09:15:42 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> I expect the caller to keep the file only for a while when it is
>> expecting that a given file is needed several times (like meta
>> information if a file in vc).
>
> I'm wondering how often the caller will be able to make use of this
> (i.e. how often it will happen that two or more calls to file-local-copy
> will require the same file and will know enough about each other to
> coordinate the file-deletion).
>
> Do you have some callers in mind?
The first idea to this came when I saw
<http://thread.gmane.org/gmane.emacs.orgmode/92856>. It offered a patch
to keep some copied remote images in a cache in order to redisplay
them.
Another evidence for such functionality is vc. If you open a remote file
under bzr control, there will be local copies of .bzr/checkout/dirstate,
.bzr/branch/format and .bzr/branch/last-revision. In the cvs case,
CVS/Entries is taken via file-local-copy. And there might be similar
cases for the other vc backends, I haven't checked. All of them are
candidates for a file cache as proposed.
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2014-12-11 9:20 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 [this message]
2014-12-11 15:22 ` Stefan Monnier
2014-12-14 10:22 ` Michael Albinus
2014-12-14 13:46 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761dik0f5.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.