Re: fast-lock-cache-name causes error
Colin Rafferty <craffert(a)ms.com> writes:
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.
This error isn't limited to crypt++ only. It can be caused by the
following steps:
1. Turn on Options/Syntax Hightlighting/Lazy+Caching
2. Press the Help button in the toolbar
3. Select the xemacs node + press enter
4. Press "q" in the help frame
5. Switch to the remaining help window (why does it exists still?)
6. Try C-x C-k
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)
The error disappeared when I removed
"(set fast-lock-mode t nil (fast-lock))".
Enrico
--
eMail: enrico.scholz(a)wirtschaft.tu-chemnitz.de
talk: ensc(a)ultra.csn.tu-chemnitz.de