Jean-Michel> I was working on a file a wanted to open an other Jean-Michel> file in a buffer when I got the warning i put in the Jean-Michel> subject of this email. I tried to open an other and Jean-Michel> got the same trouble. This is unfortunately not very helpful. The warning could occur in any function that expects a string argument. We need to know which one, and how it got passed nil instead of a string. One thing you can do to prepare is to update to the most recent version of the net-utils package. Recent versions of the emacsbug library give very detailed information about your configuration and the state of XEmacs at the time you start the bug report. If you get such a warning once, type M-: (setq debug-on-error t) RET. Then try the operation again. This will very likely produce the same error, and then will print out a trace of the functions which are active at the time of the error. This narrows the field considerably.. Finally, if this doesn't seem to help, do M-x report-emacs-bug _immediately_. This will tell us what your most recent commands have been. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

Stephen> Finally, if this doesn't seem to help, do M-x Stephen> report-emacs-bug _immediately_. APA> Make that APA> M-x report-xemacs-bug APA> instead for a latest version of the net-utils package. And if he hasn't upgraded yet? r-e-b works either way. r-x-b goes `ding!' &gratuitous_backwards_incompatibility_sucks_rant; &there_is_no_emacs_but_emacs_emacs_is_one_rant; -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."