Re: XEmacs 21.5 and dired-gets-current-buffer-wrong bug

APA> why don't you post a sample log if you don't mind. APA> Including a timestamp would provide useful information too. OK. Here goes, now from *Message-Log* using message: (Analysis!? below) ---------------------------------------------------------------------- [...] Loading dired... Loading dired-mule... Loading dired-mule...done recent-files is already initialized. Loading dired...done Reading directory /home/matsl/work/... Mon May 29 23:25:13 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:13 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:13 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:13 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:14 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook Mon May 29 23:25:15 2006 Lazy-lock-maybe:XEmacs Expected buf = work but got preIdleHook No file on this line [...] ---------------------------------------------------------------------- Explanation: I'm on the buffer preIdleHook (where I keep my code fragments in trying to sort out this problem.) While there I do {C-x d} (dired) Dired is loaded and starts to read the directory /home/matsl/work (where I keep the preIdleHook file). Now my buffer-check-code in lazy-lock-maybe-fontify-frame starts to complain repeatedly because when we go in into the function work is the current-buffer but going out preIdleHook is current. (I can't account for why this is repeated. It seems like work is found again and the lost again. Finally preIdleHook is modified and dired thinks it is looking at a dired buffer but finds no file, thus the final "No file on this line". Yours -- %% Mats