It seems so, that xemacs (21.4) does not execute an given init file, unless it is referenced with an absolut path. Files with an relative path are not processed. BYe, Oliver Oliver Fischer wrote:

Stephen J. Turnbull wrote: Files with an relative path are not processed on two of my machines. I put an init.el under /tmp with only one statement: (message "Hallo") I changed my cwd to /tmp and typed: xemacs -user-init-file init.el The message wasn't shown. Starting xemacs with an absolute path like this xemacs -user-init-file /tmp/init.el worked for my. Bye Oliver

Oliver> It seems so, that xemacs (21.4) does not execute an given Oliver> init file, unless it is referenced with an absolut Oliver> path. Files with an relative path are not processed. Stephen> Sure they are. Relative to the directory in which xemacs Stephen> was started, not the user's home directory. Stephen> If you're using -user-init-file, presumably you're trying Stephen> to achieve some special effect. I don't think it's Stephen> unreasonable for XEmacs to assume you know what you're Stephen> doing, and not issue annoying warnings, etc. Stephen, isn't that position a bit extreme? Why the hell do we need error messages in computer program if people always get things right, anyways (yeah, right)? :-) Not being able to find the file a user told us to read initializations from is definitely worth a warning in my opinion. Best regards, Adrian Stephen> -- Stephen> Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp Stephen> University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Stephen> Ask not how you can "do" free software business; Stephen> ask what your business can "do for" free software. -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/