From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 1741@emacsbugs.donarmstrong.com, Dan Nicolaescu <dann@ics.uci.edu>
Subject: bug#1741: 23.0.60; vc fail to register file while logged as /su:: with tramp
Date: Sun, 12 Apr 2009 20:15:23 +0200 [thread overview]
Message-ID: <87myalrb5w.fsf@gmx.de> (raw)
In-Reply-To: <jwvy6u97kqn.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Thu, 09 Apr 2009 14:23:37 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> I'd rather find a more generic fix. E.g. can't you flush the cache when
>>> handling process-file?
>> That would be too invasive, I believe. The whole cache would be flushed,
>> even all data which are not related too.
>
> It should be safe to only flush data related to the relevant host.
That I do already, of course.
>> And there might be the case, that a file is registered in RCS (or
>> whatever backend is used) outside Emacs. Tramp would still have stale
>> cache data for "/su:root@localhost:/tmp/RCS/blah,v" then.
>
> This is unrelated to RCS, and is indeed a real problem. For that reason
> I'd expect the cache to be flushed very often, yes. E.g. in
> post-command-hook. When do you flush it currently?
Currently, I try to avoid flushing data mostly. In fact, flushing
happens file-wise or directory-wise only, when the file or directory
changes. And also in `revert-buffer'.
What I'm thinking about is using a time-stamp for cached data. Then one
could introduce a user option `tramp-cache-ttl', which is set to the
number of seconds a cache entry shall be kept. `nil' means no flush (as
it is today); 0 means no caching at all.
A value of 5 would have already benefit, because usually there are
several calls of, for example, `file-attributes' during a short time,
because of more complex operations.
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2009-04-12 18:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200904150011.n3F0BT8Q005193@godzilla.ics.uci.edu>
2008-12-30 10:48 ` bug#1741: 23.0.60; vc fail to register file while logged as /su:: with tramp Thierry Volpiatto
2009-04-07 16:57 ` Dan Nicolaescu
2009-04-08 11:23 ` thierry.volpiatto
2009-04-08 16:24 ` Dan Nicolaescu
2009-04-08 17:53 ` Stefan Monnier
2009-04-09 13:51 ` Michael Albinus
2009-04-09 14:38 ` Stefan Monnier
2009-04-09 15:06 ` Michael Albinus
2009-04-09 18:23 ` Stefan Monnier
2009-04-12 18:15 ` Michael Albinus [this message]
2009-04-12 19:41 ` Stefan Monnier
2009-04-12 19:56 ` Michael Albinus
2009-04-12 22:51 ` Stefan Monnier
2009-04-13 9:30 ` Michael Albinus
2009-04-13 12:24 ` Stefan Monnier
2009-04-14 15:19 ` Michael Albinus
2009-04-14 17:06 ` Stefan Monnier
2009-04-15 20:55 ` Michael Albinus
2009-04-15 0:20 ` bug#1741: marked as done (23.0.60; vc fail to register file while logged as /su:: with tramp) Emacs bug Tracking System
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=87myalrb5w.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=1741@emacsbugs.donarmstrong.com \
--cc=dann@ics.uci.edu \
--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 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).