Steve Youngs <sryoungs(a)bigpond.net.au> writes:
Steven, it would probably help if you could send the output from
`M-x report-xemacs-bug RET'.
Well, this isn't going to help very much:
,----[ report-xemacs-bug failure ]
| Signaling: (void-function nil)
| nil("XEmacs Beta <xemacs-beta(a)xemacs.org>" "[Bug: 21.4.13]
Sample" nil nil nil nil nil)
| compose-mail("XEmacs Beta <xemacs-beta(a)xemacs.org>" "[Bug:
21.4.13] Sample" nil)
| #<compiled-function (topic &optional recent-keys) "...(516)" [map
before-keys user-point mods topic mail-user-agent nil "[Bug: " "] "
compose-mail re-search-forward "^" regexp-quote "$" 1
"================================================================\n" "Dear
Bug Team!\n\n"
"\n\n================================================================\n\nSystem Info
to help track down your bug:\n---------------------------------------\n\n"
Installation-string fboundp append-message (...) #<compiled-function ...
"...(2)" ... 1 "\nCommon Lisp lambda list:\n (lambda &rest
ARGS)\n\n"> clear-message (...) #<compiled-function ... "...(2)" ...
1 "\nCommon Lisp lambda list:\n (lambda &optional LABEL FRAME STDOUT-P
NO-RESTORE)\n\n"> "\n\nLoad-Path Lisp Shadows:\n"
"----------------------\n" format "%s" find-emacs-lisp-shadows
fill-paragraph t "\n" "\n\nInstalled XEmacs Packages:\n"
"-------------------------\n" cl-prettyprint packages-package-list list-modules
"\n\nInstalled Modules:\n" "-----------------\n"
"\n\nFeatures:\n--------\n\n%s" features "\n\n" "Recent
keystrokes:\n-----------------\n\n" key-description move-to-column 50 search-forward
" " ...] 5
("/usr/local/lib/xemacs/xemacs-packages/lisp/net-utils/xemacsbug.elc" . 3939)
(byte-code "ÀÁ ÂÃ!D!" [reverse recent-keys read-string "Bug Subject:
"] 4)>("Sample" [#<keypress-event c> #<keypress-event o>
#<keypress-event m> #<keypress-event p> #<keypress-event o>
#<keypress-event s> #<keypress-event e> #<keypress-event ->
#<keypress-event m> #<keypress-event a> #<keypress-event i>
#<keypress-event l> #<keypress-event return> #<keypress-event control-P>
#<keypress-event control-E> #<keypress-event control-A> #<keypress-event
q> #<misc-user-event (cancel-mode-internal nil)> #<keypress-event (>
#<keypress-event r> #<keypress-event e> #<keypress-event p>
#<keypress-event o> #<keypress-event r> #<keypress-event t>
#<keypress-event -> #<keypress-event x> #<keypress-event e>
#<keypress-event m> #<keypress-event a> #<keypress-event c>
#<keypress-event s> #<keypress-event -> #<keypress-event b>
#<keypress-event u> #<keypress-event f> #<keypress-event space>
#<keypress-event backspace> #<keypress-event backspace> #<keypress-event
g> #<keypress-event space> #<keypress-event '> #<keypress-event
shift-backspace> #<keypress-event "> #<keypress-event F>
#<keypress-event o> #<keypress-event o> #<keypress-event ">
#<keypress-event )> #<keypress-event control-X> ...])
| call-interactively(report-xemacs-bug)
| command-execute(report-xemacs-bug t)
| execute-extended-command(nil)
| call-interactively(execute-extended-command)
`----
Oh, now if I execute (load-library "gnus"), we get this:
And I'd like to see the values of `user-init-file',
`user-init-directory'.
user-init-file: "/home/sharr/.xemacs/init.el"
user-init-directory: "~/.xemacs/"
If you see differences between bug reports of mine with my home path
looking slightly different, it's because it's /home/sharr at work and
/home/seh at home. Otherwise, the setups are the same.
--
Steven E. Harris