running-temacs-p vs. pdump

There's at least two different ways to tell the current initialization state. - initialized - Frunning_temacs_p() There's lots of different ways to run xemacs - Run undumped temacs using temacs -batch -l loadup.el run-temacs ARGS... This comes in pdump and non-pdump flavors. - Run classic dumped xemacs using xemacs ARGS... - Run pdumped xemacs using xemacs ARGS... The meaning of things like initialized are, to me, fuzzy at best. What does (running-temacs-p) mean, exactly? It sure seems like a bug to me that ./xemacs -batch -eval '(progn (print (running-temacs-p)))' ==> t ; if xemacs is configured ---pdump ==> nil ; if xemacs is configured without --pdump This will potentially affect all code that calls (runing-temacs-p). Fortunately there aren't very many calls. ./lisp/paths.el:151: (if (running-temacs-p) ./lisp/paths.el:275:(if (running-temacs-p) ./src/fileio.c:706: if (NILP (Frunning_temacs_p ())) What is the effect? Here's one bug: with pdump: (martin＠polgar) /usr/local/x/build/mpps/src $ ./xemacs -batch -eval '(message "%s %s" (make-temp-name "foo") (make-temp-name "foo"))' fooWdDWXY fooWdDWXY without pdump: (martin＠polgar) /usr/local/x/build/mps/src $ ./xemacs -batch -eval '(message "%s %s" (make-temp-name "foo") (make-temp-name "foo"))' fooXdD_XY fooXdDgqm