re:Problems with verify-visited-file-modtime in Lemacs 19.10
jeff (jsparkes@bnr.ca)
Mon, 27 Jun 1994 10:22:00 -0400
In message "Problems with verify-visited-file-modtime in Lemacs 19.10",
'sandy@ibm550.sissa.it' writes:
>We've had a couple of reports that with both dired and efs loaded,
>Lucid Emacs 19.10 issues repeated warnings that the disk copies of
>files have changed, when in fact they haven't. It seems to be some
>problem with the handler for verify-visited-file-modtime not running
>when it should. I suspect that this is a Lemacs bug, as this problem
>is not occuring with FSF Emacs 19, and the file-name-handler interface
>is supposed to identical between the two.
>
>Another possibility is that it might be related to the file-truename
>business. That's done differently in FSF and Lucid.
>
>Has anybody figured out what is causing this? Or at least, can people
>send me some more clues so that we can track this down? It would be
>good to get a patch together to send to Jamie asap.
I've only seen this behaviour on *local* files, which means that the
efs-verify-visited-file-modtime shouldn't and isn't being called for
that file; this means the blame if probably the dired-fn-handler,
which is called for *all* files.
I also get crashes in garbage collection that seem to be happening in
the bq-iterative-list-builder function of macros.
A test case that I've found reliable is my first access to
/ftp@sunsite.unc.edu:pub/packages
(I found the crash in macros by setting gc-cons-threshold to 0, and
doing a find-file on that directory.)
--
Jeff Sparkes
jsparkes@bnr.ca Bell-Northern Research, Ottawa, Ontario, Canada