Re: efs 1.14 and XEmacs 19.12
Andy Norman (ange@hplb.hpl.hp.com)
Tue, 18 Jul 1995 16:57:20 +0100
Jin writes:
> Visit a non-local directory in dired using efs and xemacs. Hit 'f' on a
> file, and it will say something about 0 not being a cons.
> Here is a backtrace:
> Signalling: (wrong-type-argument consp 0)
> set-visited-file-modtime(0)
> efs-set-emacs-bvf-mdtm(#<buffer "README@tsx-11"> 0)
> (if (efs-save-match-data (and efs-verify-modtime-host-regexp ... ... ...)) (efs-send-cmd host user (list ... ... file) nil nil (efs-cont ... ... ...) 0) (efs-set-emacs-bvf-mdtm buffer 0)))
> (let* ((path buffer-file-name) (parsed ...) (host ...) (user ...) (file ...) (buffer ...)) (if (efs-save-match-data ...) (efs-send-cmd host user ... nil nil ... 0) (efs-set-emacs-bvf-mdtm buffer 0)) nil))
> (if time (efs-set-emacs-bvf-mdtm (current-buffer) time) (let* (... ... ... ... ... ...) (if ... ... ...) nil)))
> efs-set-visited-file-modtime()
This seems to be an efs bug. The next version of efs to be released already
has the fix. The problem is that set-visited-file-modtime under XEmacs
requires a cons of integers (time-list) and efs only passes one value.
A workaround is to look for all calls to efs-set-emacs-bvf-mdtm in efs.el and
change the second argument from 0 to '(0 0).
-- ange -- <><
ange@hplb.hpl.hp.com