Stephen J. Turnbull wrote:
>>>>>"Oliver" == Oliver Fischer
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.
Sure they are. Relative to the directory in which xemacs was started,
not the user's home directory.
Files with an relative path are not processed on two of my machines.
I put an init.el under /tmp with only one statement:
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.