Re: fast-lock-cache-name causes error

Monday, 25 January 1999

        Colin Rafferty <craffert(a)ms.com&gt; 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998