Ailin Nemui <ailin.nemui(a)gmail.com> writes:
> Do you mean the file is changed outside XEmacs?
yep, it is changed on the remote server with another editor (happens to
be also xemacs but shouldn't matter ;) )
Well, one of the new features in Tramp is caching of file
attributes. You should have seen the performance improvement :-)
The dark side are stale caches. You can control Tramp's caching
behaviour by the variable `remote-file-name-inhibit-cache'. This is a
GNU Emacs variable, which is acknowledged by Tramp. Maybe it shall also
be introduced in XEmacs 21.5. Its definition is
--8<---------------cut here---------------start------------->8---
remote-file-name-inhibit-cache is a variable defined in `files.el'.
Its value is 10
Documentation:
Whether to use the remote file-name cache for read access.
When `nil', never expire cached values (caution)
When `t', never use the cache (safe, but may be slow)
A number means use cached values for that amount of seconds since
caching.
The attributes of remote files are cached for better performance.
If they are changed outside of Emacs's control, the cached values
become invalid, and must be reread. If you are sure that nothing
other than Emacs changes the files, you can set this variable to `nil'.
If a remote file is checked regularly, it might be a good idea to
let-bind this variable to a value less than the interval between
consecutive checks. For example:
(defun display-time-file-nonempty-p (file)
(let ((remote-file-name-inhibit-cache (- display-time-interval 5)))
(and (file-exists-p file)
(< 0 (nth 7 (file-attributes (file-chase-links file)))))))
--8<---------------cut here---------------end--------------->8---
In your case, either set this variable to `t', or to an appropriate
number you feel able to deal with. GNU Emacs' default of 10 might be a
good compromise.
Best regards, Michael.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta