Re: XEmacs nox11 startup issue

Hauke Fath <[email protected]> Tue, 10 Nov 2015 20:56:57 +0100
Newsgroups gmane.emacs.xemacs.beta
Organization TU Darmstadt
Message-ID <[email protected]>
On Wed, 11 Nov 2015 02:59:16 +0900, Stephen J. Turnbull wrote:
> However I suspect it will be more effective and less painful to just
> post the error and the Lisp backtrace here (and if it crashed, which I
> don't think it should do at that point, the C backtrace) here.

It didn't crash. I added a

(debug)

to guided-tour-find-menubar-help-menu, and traced from there, and 
(after dealing with the empty menubar and default-menubar vars) 
eventually ran into the mentioned

Debugger entered--Lisp error: (wrong-type-argument consp nil) 
  signal(wrong-type-argument (consp nil)) 
  signal-error(wrong-type-argument (consp nil)) 
  normal-top-level() 

around frame.el:392		(set-frame-properties frame-initial-frame newprops)

I figured that slipping a (debug) in frame.el might speed up things, 
and then found that it gets dumped with xemacs.

Cheerio,
Hauke

-- 
     The ASCII Ribbon Campaign                    Hauke Fath
()     No HTML/RTF in email            Institut für Nachrichtentechnik
/\     No Word docs in email                     TU Darmstadt
     Respect for open standards              Ruf +49-6151-16-3281