Re: Help debugging

nbecker> Anyone have any clue what this is? nbecker> Value: "21.1 (patch 12) \"Channel Islands\" XEmacs Lucid" nbecker> Signaling: (void-function null-buffer-file-name) nbecker> signal(void-function (null-buffer-file-name)) nbecker> byte-code("..." [kill-buffer buf signal data] 3) nbecker> find-file-noselect("/home/nbecker/balmail.tar.gz") nbecker> find-file("/home/nbecker/balmail.tar.gz") nbecker> #<compiled-function nil "...(8)" [t find-file-run-dired find-file dired-get-filename] 2 ("/usr/local/lib/xemacs/xemacs-packages/lisp/dired/dired.elc" . 61862) nil>() nbecker> call-interactively(dired-advertised-find-file) Hmmh, my best guess would be that some (null buffer-file-name) got accidentally changed into (null-buffer-file-name) somewhere in the code-base you built from. I have searched cd d:\tmp\21.1\xemacs\lisp\ find . -name "*.el" -exec grep -n "null-buffer-file-name" {} ;[1] and cd c:\XEmacs\xemacs-packages\lisp\ find . -name "*.el" -exec grep -n "null-buffer-file-name" {} ; and found nothing. I have almost all the latest packages installed too! Try doing the same search. Hope this helps, Adrian Footnotes: [1] find . -name "*.el" -exec grep -n "null-buffer-file-name" {} \; should work on UNIX. I use Cygwin on WindowsNT, where ... {} ; works. -- Adrian Aichner <adrian(a)xemacs.org&gt;