Re: fast-lock-cache-name causes error
Enrico Scholz writes:
if "buffer-file-name" in fast-lock.el:529, v3.11.01 is nil
(I don't
know why it happens, but it happens) "expand-file-name" will be called
with nil which causes an error.
There is a comment in the code that mentions that crypt++ can cause
this to happen. However, since I don't use fast-lock, I am not
competent to fix the code.
However, since you are using a post-20.4 XEmacs, you may want to
switch to using lazy-shot instead of fast-lock. It doesn't save .flc
files, and it works very well.
(add-hook 'font-lock-mode-hook 'turn-on-lazy-shot)
--
Colin