From xemacs-m  Wed Apr  9 23:41:29 1997
Received: from beavis.bayserve.net (jmiller@port35.bayserve.net [206.148.244.133])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id XAA18260
	for <xemacs-beta@xemacs.org>; Wed, 9 Apr 1997 23:41:12 -0500 (CDT)
Received: (from jmiller@localhost)
          by beavis.bayserve.net (8.8.4/8.8.4)
	  id AAA01638; Thu, 10 Apr 1997 00:45:20 -0400
Date: Thu, 10 Apr 1997 00:45:20 -0400
Message-Id: <199704100445.AAA01638@beavis.bayserve.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Jeff Miller <jmiller@bayserve.net>
To: xemacs-beta@xemacs.org
Subject: Re: modeline.el customized
In-Reply-To: <kig4tdhh9i8.fsf@jagor.srce.hr>
References: <kig4tdhh9i8.fsf@jagor.srce.hr>
X-Mailer: VM 6.23 under 20.1 XEmacs Lucid (beta11)
Reply-to: jmiller@bayserve.net
X-Face: &vGrMZ?Q&W5~yiCR_#hat=$tgJrK`J=2$se?0Nu9I3G|I<2-\:82zx>kz=l8(yw)G1i&0"D
 <nv_e$^;,ftG6@Hn"did"G5i=X_-Z3Y

>>>>> "Hrv" == Hrvoje Niksic <hniksic@srce.hr> writes:

I tried out the modeline & minibuf patches. but when I try to redump
xemacs, I get this:

Loading abbrev... (6784)
Loading derived... (4296)
Loading minibuf...*** Error in XEmacs initialization
(void-function custom-declare-group)
*** Backtrace
  really-early-error-handler((void-function custom-declare-group))
  custom-declare-group(minibuffer nil "Minibuffer customizations" :group environment)
  byte-code("%&" [custom-declare-group minibuffer nil "Minibuffer customizations" :group environment custom-declare-variable insert-default-directory t "*Non-nil means when reading a filename start with default dir in minibuffer." :type boolean] 8)
  # bind (current-load-list standard-input)
  # (unwind-protect ...)
  # bind (load-file-name)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  load("minibuf")
  (prog1 (load "minibuf") (garbage-collect))
)
  (load-gc "minibuf")
)

I'm no lisp expert, but it looks to me like maybe the custom stuff needs
to be dumped or whatever such that it is available at the very early
stages when xemacs starts up.  

but, then again, I could be wrong. 

