XEmacs 21.4.4 crashes when started with "xemacs -nw -f gnus"
22 years, 8 months
Eric Knauel
Eric Knauel
This bug report will be sent to the XEmacs Development Team,
not to your local site managers!!
Please write in English, because the XEmacs maintainers do not have
translators to read other languages for them.
In XEmacs 21.4 (patch 4) "Artificial Intelligence" [Lucid] (i386-unknown-freebsd4.3) of Mon Jul 30 2001 on galibier
configured using `configure --with-prefix=no --site-includes=/afs/informatik.uni-tuebingen.de/i386_fbsd32/include --site-libraries=/afs/informatik.uni-tuebingen.de/i386_fbsd32/lib --with-menubars=lucid --with-scrollbars=lucid --with-xpm --with-jpeg --with-png --with-dialogs=athena --with-widgets=athena --mail-locking=file --pdump'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
Hi,
when I type "xemacs -nw -f gnus" to start XEmacs within a xterm to
quickly check my mail it crashes. I'm not sure if this is XEmacs'
fault because it works without "-f gnus" option. However, my gnus (a
recent CVS version) works fine when I start XEmacs without "-nw".
This confuses me and I'm not sure if this the right place to ask what
I can about that. So please excuse me if I'm wrong and this is the
fault of gnus. ;-)
BTW I can reproduce the crash. The c backtrace some non-ASCII
characters which mail-mode converted to hexadecimal characters. I hope
that this will be no problem.
This is the Lisp backtrace:
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, please report this bug by running the send-pr
script included with XEmacs, or selecting `Send Bug Report'
from the help menu.
As a last resort send ordinary email to `crashes(a)xemacs.org'.
*MAKE SURE* to include the information in the command
M-x describe-installation.
If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called `core' and is located in the
directory in which you started the editor, or maybe in your home
directory), and type
gdb /afs/wsi/i386_fbsd43/bin/xemacs core
then type `where' when the debugger prompt comes up.
(If you don't have GDB on your system, you might have DBX,
or XDB, or SDB. A similar procedure should work for all of
these. Ask your system administrator if you need more help.)
Lisp backtrace follows:
# bind (form)
gnus-byte-compile((lambda (file orig-file) (nnmail-split-incoming file (quote nnml-save-mail) (quote nil) (if ... nil ...) (quote nnml-active-number))))
# bind (source incomings incoming total new i group-in fetching-sources sources spool-func group temp exit-func method)
nnmail-get-new-mail(nnml nnml-save-nov "~/Mail/" nil)
# bind (server group)
nnml-request-scan(nil "")
# bind (gnus-command-method gnus-inhibit-demon mail-source-plugged gnus-command-method group)
gnus-request-scan(nil (nnml ""))
# bind (where mesg force method)
gnus-read-active-file-1((nnml "") nil)
# (condition-case ... . ((quit (message "Quit reading the active file"))))
# (unwind-protect ...)
# bind (methods method not-native force)
gnus-read-active-file(nil nil)
# bind (init nnmail-fetched-sources dont-connect level rawfile)
gnus-setup-news(nil nil nil)
byte-code("..." [gnus-slave gnus-current-startup-file gnus-startup-file did-connect level dont-connect gnus-group-quit gnus-run-hooks gnus-startup-hook gnus-make-newsrc-file gnus-dribble-read-file bbb-login add-hook gnus-summary-mode-hook gnus-grouplens-mode gnus-setup-news nil gnus-setup-news-hook gnus-start-draft-setup gnus-group-list-groups gnus-group-first-unread-group gnus-configure-windows group gnus-group-set-mode-line gnus-started-hook gnus-use-dribble-file gnus-use-grouplens] 4)
# bind (level did-connect slave dont-connect arg)
gnus-1(nil nil nil)
# bind (slave dont-connect arg)
gnus()
# bind (arg)
command-line-do-funcall("-f")
# bind (dir file-count line end-of-options file-p arg tem)
command-line-1()
# bind (command-line-args-left)
command-line()
# (unwind-protect ...)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
Segmentation fault (core dumped)
This is what GDB says:
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
Core was generated by `xemacs-21.4.4'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/X11R6/lib/libXaw.so.7...done.
Reading symbols from /usr/X11R6/lib/libXpm.so.4...done.
Reading symbols from /usr/X11R6/lib/libXmu.so.6...done.
Reading symbols from /usr/X11R6/lib/libXt.so.6...done.
Reading symbols from /usr/X11R6/lib/libXext.so.6...done.
Reading symbols from /usr/X11R6/lib/libX11.so.6...done.
Reading symbols from /usr/X11R6/lib/libSM.so.6...done.
Reading symbols from /usr/X11R6/lib/libICE.so.6...done.
Reading symbols from /usr/lib/libncurses.so.5...done.
Reading symbols from /usr/lib/libm.so.2...done.
Reading symbols from /usr/lib/libutil.so.3...done.
Reading symbols from /usr/lib/libxpg4.so.3...done.
Reading symbols from /usr/lib/libc.so.4...done.
Reading symbols from /usr/libexec/ld-elf.so.1...done.
#0 0x284888e8 in kill () from /usr/lib/libc.so.4
(gdb) where
#0 0x284888e8 in kill () from /usr/lib/libc.so.4
#1 0x80a8e9b in fatal_error_signal (sig=11) at emacs.c:535
#2 0xbfbfffac in ?? ()
#3 0x808c33b in funcall_compiled_function (fun=138835016, nargs=1, args=0xbfbfde9c) at bytecode.c:515
#4 0x80b039b in Ffuncall (nargs=2, args=0xbfbfde98) at eval.c:3563
#5 0x808c623 in execute_optimized_program (
program=0x8767e10 "\016>®\r\0168<«\005\0168ª\004\0168C\031Æ\e\0169\036?Ç\211\036:\036;Ç\032Æ\211\036＠\036AÆ\035ÈÉ\f\"\203\203", stack_depth=17, constants_data=0x863b810) at bytecode.c:746
#6 0x808c33b in funcall_compiled_function (fun=141134920, nargs=4, args=0xbfbfe004) at bytecode.c:515
#7 0x80b039b in Ffuncall (nargs=5, args=0xbfbfe000) at eval.c:3563
#8 0x808c623 in execute_optimized_program (program=0x84e26d0 "Ä\022Å\013\t\"\210ÆÇÈ\b\013$\207",
stack_depth=5, constants_data=0x87b1050) at bytecode.c:746
#9 0x808c33b in funcall_compiled_function (fun=142127976, nargs=2, args=0xbfbfe144) at bytecode.c:515
#10 0x80b039b in Ffuncall (nargs=3, args=0xbfbfe140) at eval.c:3563
#11 0x808c623 in execute_optimized_program (
program=0x87eb610 "\f«\006Æ\f!ª\002\rÇ\n\031\030\035\n¬\aÈ\r!?\035É\rÊ\"\f\022\f\eËÌ\013\"«\b\013Í\225ÎOª\002\013)\rA＠\"+\207", stack_depth=4, constants_data=0x8611090) at bytecode.c:746
#12 0x808c33b in funcall_compiled_function (fun=140431164, nargs=2, args=0xbfbfe284) at bytecode.c:515
#13 0x80b039b in Ffuncall (nargs=3, args=0xbfbfe280) at eval.c:3563
#14 0x808c623 in execute_optimized_program (
program=0x87db010 "Æ\211\0366\0367\rA＠\0267ÇÈ\0167«\016\0167GÉU¬\aÊ\0167Pª\002Ë\r＠#\0266ÌÍ\0166\"\210Î\r!\205Ñ\002Ï\r＠\034\036>ÆÐÑ\217*«\006ÒÆ\r\"\210\016CÓa\203\204\002Ô\r＠\034\036>ÆÕÖ\217*\203v\002\016D\204q\002\016EAÆ\r\035\034\r;«\006×\r!ª\\\r\0162k«\005\0162ªR\r＠;«\n\f«\aØ\f\r\"ªD\r«\016\f¬\013\rA＠Ëk«\004\rª4\r\035Ù\r＠!\031ÚÛ\t\0169\"s«\"Ü\tÝP!\r·¬\031Þ\r＠\0169·s«\020ß\rÜ\tÝP!\rA＠DC\"ª\002\r**"...,
stack_depth=7, constants_data=0x8659c10) at bytecode.c:746
#15 0x808c33b in funcall_compiled_function (fun=140933768, nargs=2, args=0xbfbfe32c) at bytecode.c:515
#16 0x80afb39 in Feval (form=140922384) at eval.c:3388
#17 0x80ad111 in condition_case_3 (bodyform=140922384, var=676427124, handlers=140922156)
at eval.c:1651
#18 0x808ceba in execute_rare_opcode (stack_ptr=0xbfbfe548, program_ptr=0x87aea48 "\210ªì+\207",
opcode=Bcondition_case) at bytecode.c:1271
#19 0x808c4b7 in execute_optimized_program (
program=0x87aea10 "Æ \210ÇÈÉ\t¬\013Ê\013!«\006\013\nBª\002\nË \003ÌC\"\"Í\034\035Í\020\212\016\020q\210\r\211A\025＠\211\024\r\f\r¶¬óÍÎÏ\217\210ªì+\207", stack_depth=5, constants_data=0x8650310)
at bytecode.c:656
#20 0x808c33b in funcall_compiled_function (fun=140933740, nargs=2, args=0xbfbfe684) at bytecode.c:515
#21 0x80b039b in Ffuncall (nargs=3, args=0xbfbfe680) at eval.c:3563
#22 0x808c623 in execute_optimized_program (
program=0x8793e10 "ÆÇ!\210\016#\a\t\004\016$??ÈC\036'\211\e«\013É\211\026#\021Ê\016$!\210\016%«\020ËÌÍ\n\"\n\"\022Í\016%B\nB\022\r«\006\rÎa«\004Ï \210\r«\t\f¬\006ÅÉ\b\"\210\t¬\005ÐÑ!\021\016(«\004Ò \210\013«\f\016)¬\005\016\"«\004Ó \210\013«\b\016\"«\004Ô \210Õ \210Ö×!«\036\016\027;«\031É\036*ØÙ\016\027\")«\016\016+¬\n\b¬\a\r«\004Ú \210\013«\031\016,«\025\f¬\022Û\016&!«\f\016\"¬\b\016-«\004Ü \210\013«\024\016\036«\020\r«\r\f¬\nÝ\016&!«\004Þ \210\016."..., stack_depth=5, constants_data=0x8655b10)
at bytecode.c:746
#23 0x808c33b in funcall_compiled_function (fun=140844916, nargs=3, args=0xbfbfe7c4) at bytecode.c:515
#24 0x80b039b in Ffuncall (nargs=4, args=0xbfbfe7c0) at eval.c:3563
#25 0x808c623 in execute_optimized_program (
program=0xbfbfe81c "\r¬\t\013¬\006Æ \210ª>ÇÈ!\210É\n!\021\b¬\005\016\031«\004Ê \210\016\032«\tË \210ÌÍÎ\"\210ÏÐ\f\r#\210ÇÑ!\210Ò \210Ó\f!\210Ô \210ÕÖ!\210× \210ÇØ!\210Ð\2071\ba«\fÙ\001", stack_depth=4,
constants_data=0x8650690) at bytecode.c:746
#26 0x808e40a in Fbyte_code (instructions=140558916, constants=140838528, stack_depth=9)
at bytecode.c:2403
#27 0x80af8c5 in Feval (form=140919400) at eval.c:3331
#28 0x80b5ba9 in Fprogn (args=140919712) at eval.c:775
#29 0x80b5e47 in unbind_to_hairy (count=17) at eval.c:4977
#30 0x808c6b8 in execute_optimized_program (
program=0x8611990 "Æ «\025Ç\t!\210È\r§\n\rÉV\005\b＠\r]!\207Ê \210Ë \210ÌÍ!\210Î \210\016\031\026\032Ï \210\f«\034Ð\024ÑÒ!«\006Ó \210ª\020\016\e«\fÔ Õ TU«\004Ö \210\r§\a\rÉV\002\rÐ\e\032×\216\016\034?\nØ\r\003\n?!\211\023+\207s a pie\026", stack_depth=3, constants_data=0x8655d10) at bytecode.c:759
#31 0x808c33b in funcall_compiled_function (fun=140844608, nargs=3, args=0xbfbfeba4) at bytecode.c:515
#32 0x80b039b in Ffuncall (nargs=4, args=0xbfbfeba0) at eval.c:3563
#33 0x808c623 in execute_optimized_program (program=0x863d8b0 "Ã\n\t\b#\207", stack_depth=4,
constants_data=0x8551830) at bytecode.c:746
#34 0x808c33b in funcall_compiled_function (fun=139759476, nargs=0, args=0xbfbfece4) at bytecode.c:515
#35 0x80b039b in Ffuncall (nargs=1, args=0xbfbfece0) at eval.c:3563
#36 0x808c623 in execute_optimized_program (program=0x86242b0 "Á\b\211A\020＠! \207", stack_depth=3,
constants_data=0x2857f184) at bytecode.c:746
#37 0x808c33b in funcall_compiled_function (fun=677284356, nargs=1, args=0xbfbfee14) at bytecode.c:515
#38 0x80b039b in Ffuncall (nargs=2, args=0xbfbfee10) at eval.c:3563
#39 0x808c623 in execute_optimized_program (program=0x8645610 "\n¬＠\016!?\205Ñ", stack_depth=7,
constants_data=0x2857dcdc) at bytecode.c:746
#40 0x808c33b in funcall_compiled_function (fun=677282256, nargs=0, args=0xbfbfef54) at bytecode.c:515
#41 0x80b039b in Ffuncall (nargs=1, args=0xbfbfef50) at eval.c:3563
#42 0x808c623 in execute_optimized_program (
program=0x837de10 "\013A\035ÆÇ\032\031È\r!\025ÉÊ!«\004Ë \210\f«\016\b¬\013ÌÍÎ\f!ÏQ! \210Ð \210*Ñ \210Ò \210rÓÔ!q\210Õ \210Ö×!\210\016\036Øa«\005\016\037 \210)Ù Úa«\bÀ ¬\004Û \210Ü \210×\026 À \004ÝÇ!)\207 right place in\aÐ7\b", stack_depth=4, constants_data=0x2857e598) at bytecode.c:746
#43 0x808c33b in funcall_compiled_function (fun=677283012, nargs=0, args=0xbfbff094) at bytecode.c:515
#44 0x80b039b in Ffuncall (nargs=1, args=0xbfbff090) at eval.c:3563
#45 0x808c623 in execute_optimized_program (
program=0x832d410 "\t«\005ÆÇ!\207È\021É \211\034«\025\fG\rGW«\016Ê\r!Ê\f!k«\005Ë\f!\025)Ì\r!\025Í \210Î \210\013®\aÏÐ!\002È\eÑ\016#\016$\"\022\013«\tÒÓÔ\n\"Õ\"\210\n¬\004Ö \210×\n\016%\b\016&\013%\210Ø \210)\016!¬\022\016\"«\016ÙÚÛ\016'!\016\"\"ÜÈ#\210\016!¬\023\b¬\006Ý\016(!\210Ý\016)!\210Ý\016*!\210Þ\216ß \210)\016+\003à \207", stack_depth=7, constants_data=0x2857ef20) at bytecode.c:746
#46 0x808c33b in funcall_compiled_function (fun=677284132, nargs=0, args=0xbfbff13c) at bytecode.c:515
#47 0x80afb39 in Feval (form=676501656) at eval.c:3388
#48 0x80b5931 in condition_case_1 (handlers=676426764, bfun=0x80af21c <Feval>, barg=676501656,
hfun=0x809479c <cmd_error>, harg=676427124) at eval.c:1651
#49 0x8094823 in top_level_1 (dummy=676427124) at cmdloop.c:206
#50 0x80b583c in internal_catch (tag=676252260, func=0x80947f4 <top_level_1>, arg=676427124, threw=0x0)
at eval.c:1317
#51 0x8094116 in initial_command_loop (load_me=676427124) at cmdloop.c:285
#52 0x80aa186 in xemacs_21_4_4_i386_unknown_freebsd4_3 (argc=4, argv=0xbfbff4a8, envp=0xbfbff4bc,
restart=0) at emacs.c:2344
#53 0x80abd26 in main (argc=4, argv=0xbfbff4a8, envp=0xbfbff4bc) at emacs.c:2711
#54 0x80800c5 in _start ()
(gdb) quit
Recent keystrokes:
button1 button1up misc-user
Recent messages (most recent first):
Loading emacsbug...done
Loading emacsbug...
Fontifying *scratch*... done.
Loading advice...done
Fontifying *scratch*... (syntactically).
Fontifying *scratch*...
Loading advice...
Paren mode is paren
Loading paren...done
Loading paren...
Ciao,
Eric
--
"Excuse me --- Di Du Du Duuuuh Di Dii --- Huh Weeeheeee" (Albert King)
- 1 participants
- 0 comments
Re: W3 display through VM of this message (was Re: Bugs in artificial intelligence version (5))
22 years, 8 months
Charles Hines
Charles Hines
>>>>> "Jeff" == Jeff Mincy <jeff(a)delphioutpost.com> writes:
Jeff> Try
Jeff> (setq vm-auto-displayed-mime-content-type-exceptions '("text/html"))
Actually, I've tried that. With that I still have to hit 'D' to get the text
to show up, so it doesn't buy me anything and I have the added inconvenience
of not automatically seeing the other html formatted email that doesn't have
problems without hitting 'D'.
Of course, I personally believe that html formatted email is evil, but still
have to live with it being sent to me occasionally...
Now if I had a way to say "if multipart/alternative and text/plain is present,
that takes precidence over text/html", that'd be great. But I couldn't find
any way to do that. If I had the time I'd hack up some of the VM code to get
that functionality, but I was hoping that perhaps I was just missing something
and this could already be done somehow.
Thanks,
Chuck
--
Charles K. Hines <ckh(a)requesttech.com> <hines(a)gderome.com>
Principal Scientist at ReQuest Technologies Inc (http://www.ReQuestTech.com/)
Martial Arts Instructor [Modern Arnis and Balintawak Escrima]
"Go back to sleep, Chuck. You're just havin' a nightmare
-- of course, we ARE still in Hell." (Gary Larson)
- 2 participants
- 1 comments
egags.el does not support include's
22 years, 8 months
Enrico Scholz
Enrico Scholz
This bug report will be sent to the XEmacs Development Team,
not to your local site managers!!
Please write in English, because the XEmacs maintainers do not have
translators to read other languages for them.
In XEmacs 21.4 (patch 4) "Artificial Intelligence" [Lucid] (i386-redhat-linux, Mule) of Tue Jul 31 2001 on delenn.ultra.csn.tu-chemnitz.de
configured using `configure i386-redhat-linux --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --datadir=/usr/lib --libdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --dynamic '--cflags=-O2 -march=i386 -mcpu=i686' --debug=no --error-checking=none --with-menubars=lucid --with-scrollbars=lucid --with-dialogs=lucid --infodir=/usr/share/info/ --with-mule --with-xfs --with-xim --with-gif --with-site-lisp=no --with-toolbars=yes --without-gnome --with-ipv6-cname=no --with-sound=esd,nonative'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
When a TAGS file includes another one, `find-tag' (M-.) fails with
| Signaling: (error "Bad TAGS file")
| signal(error ("Bad TAGS file"))
| cerror("Bad TAGS file")
| apply(cerror "Bad TAGS file" nil)
| error("Bad TAGS file")
| add-to-tag-completion-table()
| byte-code("..." [tag-table-completion-status add-to-tag-completion-table t] 1)
| get-tag-table-buffer("/tmp/tags/TAGS")
| #<compiled-function (name) "...(23)" [name file-directory-p file-name-as-directory "TAGS" file-readable-p symbol-value-in-buffer buffer-file-name get-tag-table-buffer] 4>("/tmp/tags/TAGS")
| mapcar(#<compiled-function (name) "...(23)" [name file-directory-p file-name-as-directory "TAGS" file-readable-p symbol-value-in-buffer buffer-file-name get-tag-table-buffer] 4> ("/tmp/tags/TAGS"))
| buffer-tag-table-list()
| buffer-tag-table-symbol-list()
| find-tag-tag("Find tag: ")
| byte-code("..." [current-prefix-arg (nil nil) find-tag-tag "Find tag: " nil] 2)
| call-interactively(find-tag)
An example is:
----------------
$ cat >configure.in <<EOF
AC_INIT(intl/bindtextdom.c)
AM_INIT_AUTOMAKE(foo,0.0.1)
AC_OUTPUT(Makefile intl/Makefile)
EOF
$ cat >Makefile.am <<EOF
SUBDIRS = intl
EOF
$ gettextize -f
$ automake --foreign -a
$ aclocal; autoconf; ./configure
[... some messages ...]
$ make tags
$ xemacs Makefile.am
--> M-.
---------------
The TAGS file of this example contains
| ^L
| /tmp/tags/intl/TAGS,include
When removing the last line all things are ok.
Tested with xemacs-21.4.4, automake-1.4p5, autoconf-2.13 and
gettext-0.10.38.
Enrico
- 2 participants
- 3 comments
Build fails if same version is already installed
22 years, 8 months
Enrico Scholz
Enrico Scholz
This bug report will be sent to the XEmacs Development Team,
not to your local site managers!!
Please write in English, because the XEmacs maintainers do not have
translators to read other languages for them.
In XEmacs 21.4 (patch 4) "Artificial Intelligence" [Lucid] (i386-redhat-linux, Mule) of Tue Jul 31 2001 on delenn.ultra.csn.tu-chemnitz.de
configured using `configure i386-redhat-linux --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --datadir=/usr/lib --libdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --dynamic '--cflags=-O2 -march=i386 -mcpu=i686' --debug=no --error-checking=none --with-menubars=lucid --with-scrollbars=lucid --with-dialogs=lucid --infodir=/usr/share/info/ --with-mule --with-xfs --with-xim --with-gif --with-site-lisp=no --with-toolbars=yes --without-gnome --with-ipv6-cname=no --with-sound=esd,nonative'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
While rebuilding xemacs from scratch when the same version is already
installed, the build fails with:
| $ make
| ...
| Loading /var/volatile/tmp/xe/xemacs-21.4.4/lisp/dumped-lisp.el...
| rm -f ../lib-src/DOC; \
| ./temacs -nd -batch -l /var/volatile/tmp/xe/xemacs-21.4.4/src/../lisp/make-docfile.el -- \
| -o ../lib-src/DOC -d /var/volatile/tmp/xe/xemacs-21.4.4/src -i ../lib-src/../site-packages \
| abbrev.c alloc.c blocktype.c buffer.c bytecode.c callint.c callproc.c casefiddle.c casetab.c chartab.c cmdloop.c cmds.c console.c console-stream.c data.c device.c dired.c doc.c doprnt.c dynarr.c editfns.c elhash.c emacs.c eval.c events.c filelock.c unexelf.c balloon_help.c balloon-x.c eldap.c postgresql.c dgif_lib.c gif_io.c menubar.c scrollbar.c dialog.c toolbar.c menubar-x.c scrollbar-x.c dialog-x.c toolbar-x.c gui-x.c mule.c mule-ccl.c mule-charset.c file-coding.c input-method-motif.c realpath.c inline.c esd.c miscplay.c console-tty.c device-tty.c event-tty.c frame-tty.c objects-tty.c redisplay-tty.c cm.c terminfo.c gpmevent.c event-unixoid.c database.c sysdll.c emodules.c process-unix.c event-stream.c extents.c faces.c fileio.c filemode.c floatfns.c fns.c font-lock.c frame.c general.c glyphs.c glyphs-eimage.c glyphs-widget.c gui.c gutter.c hash.c imgproc.c indent.c insdel.c intl.c keymap.c line-number.c lread.c lstream.c macros.c marker.c md5.c minibuf.c objects.c opaque.c print.c process.c profile.c rangetab.c redisplay.c redisplay-output.c regex.c search.c select.c signal.c sound.c specifier.c strftime.c symbols.c syntax.c sysdep.c undo.c console-x.c device-x.c event-Xt.c frame-x.c glyphs-x.c objects-x.c redisplay-x.c select-x.c xgccache.c widget.c window.c
|
| Loading /var/volatile/tmp/xe/xemacs-21.4.4/src/../lisp/make-docfile.el...
| Loading very-early-lisp...
| Loading find-paths.el...
| Loading packages.el...
| Loading setup-paths.el...
| Loading dump-paths.el...
| Loading custom...
| Loading widget...
| Loading custom ...done
| Loading process...
| Loading /var/volatile/tmp/xe/xemacs-21.4.4/lisp/dumped-lisp.el...
| Error: dumped file version.el does not exist
|
| Error: dumped file paths.el does not exist
|
| Spawning make-docfile ...
| Spawning make-docfile ...done
| ./temacs -nd -batch -l /var/volatile/tmp/xe/xemacs-21.4.4/src/../lisp/loadup.el dump
|
| Loading /var/volatile/tmp/xe/xemacs-21.4.4/src/../lisp/loadup.el...
| Using load-path (/var/volatile/tmp/xe/xemacs-21.4.4/lisp)
| Using module-load-path (/var/volatile/tmp/xe/xemacs-21.4.4/modules)
| Loading very-early-lisp...
| Loading /var/volatile/tmp/xe/xemacs-21.4.4/lisp/dumped-lisp.el...
| Loading /var/volatile/tmp/xe/xemacs-21.4.4/lisp/backquote.elc...
| Loading /var/volatile/tmp/xe/xemacs-21.4.4/lisp/bytecomp-runtime.elc...
| Loading /var/volatile/tmp/xe/xemacs-21.4.4/lisp/find-paths.elc... (file find-paths.el is newer)
| Loading /var/volatile/tmp/xe/xemacs-21.4.4/lisp/packages.elc... (file packages.el is newer)
| Loading /var/volatile/tmp/xe/xemacs-21.4.4/lisp/setup-paths.elc...
| Loading /var/volatile/tmp/xe/xemacs-21.4.4/lisp/dump-paths.elc...
| Loading /usr/lib/xemacs-21.4.4/lisp/subr.elc...
| Loading /usr/lib/xemacs-21.4.4/lisp/replace.elc...
| Load file version.el: not found
| Fatal error during load, aborting
| make[1]: *** [xemacs] Error 1
| make[1]: Leaving directory `/var/volatile/tmp/xe/xemacs-21.4.4/src'
strace'ing temacs at the first command shows
------------
open("/usr/lib/xemacs/xemacs-packages/lisp/zenirc/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 6
open("/usr/lib/xemacs-21.4.4/lisp/mule/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 6
open("/usr/lib/xemacs-21.4.4/lisp/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 6
open("/usr/lib/xemacs-21.4.4/lisp/custom.elc", O_RDONLY) = 6
open("/usr/lib/xemacs-21.4.4/lisp/widget.elc", O_RDONLY) = 8
open("/usr/lib/xemacs-21.4.4/lisp/process.elc", O_RDONLY) = 6
open("/usr/src/redhat/BUILD/xemacs-21.4.4/lisp/dumped-lisp.el", O_RDONLY) = 6
------------
When renaming/removing the /usr/lib/xemacs-21.4.4 directory all things
are fine and strace tells
------------
open("/usr/lib/xemacs/xemacs-packages/lisp/zenirc/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 6
open("/usr/src/redhat/BUILD/xemacs-21.4.4/lisp/mule/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 6
open("/usr/src/redhat/BUILD/xemacs-21.4.4/lisp/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 6
open("/usr/src/redhat/BUILD/xemacs-21.4.4/lisp/custom.elc", O_RDONLY) = 6
open("/usr/src/redhat/BUILD/xemacs-21.4.4/lisp/widget.elc", O_RDONLY) = 8
open("/usr/src/redhat/BUILD/xemacs-21.4.4/lisp/process.elc", O_RDONLY) = 6
open("/usr/src/redhat/BUILD/xemacs-21.4.4/lisp/dumped-lisp.el", O_RDONLY) = 6
------------
Reason seems to be in `lisp/dump-paths.el'. There is a
| (setq lisp-directory (paths-find-lisp-directory roots))
statement which sets lisp-directory to configure-lisp-directory if
it exists[1]. Because some files needed by the build-process (e.g.
version.el) are not installed there it will fail.
I am using the attached patched (inspired by lisp/loadup.el) which fixes
it. A second patch is required for the top-level Makefile because the
XEmacs being called there has the same wrong load-path and will fail to
load some `-l...' files.
I am not sure if the patches are the best solution; perhaps a more smart
one exists. But they are working... ;)
Footnotes:
[1] see paths-find-emacs-directory in find-paths.el
Enrico
- 1 participants
- 0 comments
BUG: flyspell-mode doesn't recognize button2 on mispelled words
22 years, 8 months
Dr. Volker Zell
Dr. Volker Zell
Hi
See subject. When pressing button 2 on a mispelled highlighted word
I get the last marked text inserted at the point of the click.
C-h k in the offended buffer gives: button2 runs `mouse-track'
instead of flyspell-correct-word.
Anybody else seeing this behaviour ?
Ciao
Volker
- 2 participants
- 2 comments
Re: Progress - but no cigar [Follow up to: Problems trying to make 2.5.1--i686-pc-cygwin]
22 years, 8 months
David A. Cobb
David A. Cobb
At 7/29/01 03:59 AM (Sunday), David Starks-Browning wrote:
>On Saturday 28 Jul 01, David A. Cobb writes:
> > I did "make realclean" then manually deleted /everything/ under the build
> > directory (<source>/i686-pc-cygwin) except the build script.
>
>"build script"? Isn't it just configure, make, make install?
Pretty much. I put it in a script so I could go eat while waiting for it
to complete. It also makes it somewhat simpler to capture the log.
QUOTE
#! /bin/bash -x
pwd
type sh
ls -l /usr/bin/sh
#
cygcheck sh
cygcheck make
#
../configure i686-pc-cygwin --prefix=/usr/local/ \
--exec-prefix=/usr/local/i686-pc-cygwin/ \
--libdir=/usr/local/lib/ \
--without-x \
--with-site-lisp \
--with-database=gdbm \
--with-sound=native,noesd \
--use-union-type && \
make && \
make install
END-QUOTE
> > That did get
> > me beyond the previous error. I now find several undefined symbols
> > "_imp__dbm_*" which looks like a missing header in the database source(?).
>
>I had no such errors. I suspect your Cygwin installation is messed up.
OK. I did the following --
re-install gdbm (with source)
re-install Postgresql (with source)
Got rid of all remnant of previous build.
Take a day and a half trying to free enough disk space.
Ran it again.
SAME RESULT, SAME PLACE
I've attached the log.
Two things catch my eye: the error message attributes the error to the ld.
And configure claims that ld is not GNU ld. Of course, it's Cygwin; I
don't know whether that's the same.
I did determine that the "missing" symbols are in "/bin/libgdbm.dll.a" and
referenced from "<build-dir>/?/database.o".
that name is, I think, unique to Cygwin; certainly ".dll" is a windows-ism.
I'm going to copy this mail to cygwin-list in the hope that Chuck, or
someone, can clue me in whether something needs to be done to pick up that lib.
> > I also get the somewhat peculiar symptom that the configure script
> actually
> > tries to launch some x-windows function because I get a Windoze dialog
> > about not finding an "LIBX11.DLL"
>
>I noticed this too, on Win98 but not on WinNT4. Doesn't seem to cause
>any problem.
Yup. I does show, however, that configure doesn't pay much attention to my
options: having said "--without-x" IMHO configure should assume there is no
X. Period.
>This is at the top of your build log:
>
> > /usr/local/src/XEmacs/xemacs-21.5/i686-pc-cygwin
> > Error: could not find sh
> >
> > Use -h to see help about each section
/bin/sh is a symlink currently set to "/bin/bash;" evidently Cygcheck
doesn't follow the link.
> > Found: C:\#Cygwin#\bin\make.exe
> > C:\#Cygwin#\bin\make.exe
> > C:\#Cygwin#\bin\cygwin1.dll
> > C:\WINDOWS\SYSTEM\KERNEL32.dll
> >
> > Use -h to see help about each section
> > loading site script /etc/config.site
>
>a. I think we'd have to see your "build script" to make sense of
> this. I've never seen output like this directly from configure.
> In fact it looks like cygcheck output.
It is!
>b. If sh is missing, you're going to have problems!
It isn't!
>c. You've got a /etc/config.site? That's not standard. What's in it?
Then I dunno where it came from! I cerainly never wrote it.
Anyway, here it is
QUOTE
# $Header: /usr/people/sam/tiff/RCS/config.site,v 1.13 1996/06/05 21:24:33
sam Exp $
#
# TIFF Software
#
# Copyright (c) 1990-1996 Sam Leffler
# Copyright (c) 1991-1996 Silicon Graphics, Inc.
#
# Permission to use, copy, modify, distribute, and sell this software and
# its documentation for any purpose is hereby granted without fee, provided
# that (i) the above copyright notices and this permission notice appear in
# all copies of the software and related documentation, and (ii) the names of
# Sam Leffler and Silicon Graphics may not be used in any advertising or
# publicity relating to the software without the specific, prior written
# permission of Sam Leffler and Silicon Graphics.
#
# THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND,
# EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY
# WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
#
# IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR
# ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND,
# OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
# WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF
# LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
# OF THIS SOFTWARE.
#
#
# This file holds site-specific configuration parameters.
#
# Nothing is defined in here by default, the definitions
# commented out below serve as documentation for what you
# can set in this file or a config.local file.
#
# Note that you do not need to set anything here unless you
# want to override the auto-configuration behaviour and/or
# interactive prompting done by the configure script.
#
#
# Package controls.
#
#DSO="auto" # auto|IRIX|IRIX52 enable DSO support for
system
#JPEG="no" # yes|no configure JPEG support (see below)
#ZIP="no" # yes|no configure Deflate support (see below)
#LIBGL="auto" # yes|no|auto configure IRIS GL-based tools
#LIBIMAGE="auto" # yes|no|auto configure SGI RGB image tools
#HTML="no" # yes|no install HTML documentation
#
# Directory parameters.
#
#DIR_BIN="/usr/local/bin" # directory for tools
#DIR_LIB="/usr/local/lib" # directory for libraries
#DIR_INC="/usr/local/include" # directory for include files
#DIR_MAN="/usr/local/man" # directory for manual pages
#DIR_HTML="/var/httpd/htdocs/tiff" # directory for HTML documentation
#
# Configuring supporting libraries.
#
# The TIFF software makes use of two ancillary packages: the IJG
# distribution to support the JPEG codec and the zlib distribution
# to support the Deflate codec. To setup use of these packages you
# need to specify where each package's include files are located and
# where the pre-built library (static archive or DSO) is located.
# These may be different or the same (as when the package is compiled
# and referenced directly from the place where the software was
# loaded and compiled).
#
# DIRS_LIBINC is a space-separated list of directories to use for
# locating include files in these packages. Note that it should not
# include -I options as might be passed to the C preprocessor; these
# are automatically added by the configure script when the Makefiles
# are generated.
#
# DIR_<package>LIB is the pathname of the directory where <package>'s
# pre-built library may be found; this is used when building a TIFF
# DSO (on systems where support is present) and when building the
# programs in the tools directory. By default the configure script
# will load the associated library using
#
# -L${DIR_<package>LIB} -l<package>
#
# e.g. -L${DIR_JPEGLIB} -ljpeg. If this is wrong for your system
# (e.g. your compiler/loader does not support the -L option), then
# the LIB<package> parameter can be set explicitly to specify the
# library to use.
#
#
# JPEG-specific parameters; used when JPEG support is enabled (see above).
#
# JPEG support requires release 5 or later of the IJG code,
# which you can find on the Internet at ftp.uu.net:/graphics/jpeg/.
#
#DIRS_LIBINC="$DIRS_LIBINC ../src/jpeg-5a" # directory for jpeg include files
#DIR_JPEGLIB=../src/jpeg-5a # directory for libjpeg
#
# Deflate-specific parameters; used when Deflate support is enabled (see
above).
#
# NB: Deflate support requires version 0.92 or later of the zlib
# library written by Jean-loup Gailly and Mark Adler. Starting
# with about 0.95 the library is called libz.a (previously it was
# libgz.a). The library was last found at
#
# ftp://ftp.uu.net/graphics/png/code/zlib-0.93.tar.gz
#
# Look for it also at ftp://ftp.uu.net/pub/archiving/zip/zlib.
#
#DIRS_LIBINC="$DIRS_LIBINC ../zlib" # directory for zlib include files
#DIR_GZLIB="../zlib" # directory for libz
#
# Miscellaneous parameters.
#
#FILLORDER="MS2LSB" # bit order of cpu (MSB2LSB/LSB2MSB)
#MANSCHEME="sysv-source-cat-strip" # manual page installation scheme
#
# Parameters used when building the software.
#
# Note that configure has several ENVOPTS built into it that are
# set according to the target. This is done to help naive folks.
#
# Beware of changing the INSTALL definition; you *must* have an
# install script that emulates the Silicon Graphics install program!
#
#AR="/bin/ar" # pathname of suitable ar program
#AROPTS="rc" # options to ar for creating archive
#CC="gcc" # name/pathname of C compiler
#ENVOPTS="-Aa" # options for getting ANSI C
#GCOPTS="-g" # options to pass C compiler
#LIBPORT='${PORT}/libport.a' # library with emulation code
#MACHDEPLIBS="" # extra libraries for linking
#PORTFUNCS="" # non-standard functions to emulate
#RANLIB=":" # pathname of suitable ranlib program
#DSOSUF="so" # DSO filename suffix
#LIBCOPTS="-K PIC" # compiler options for building library
#
# Makefile construction parameters.
#
# These should not normally be set; configure will
# deduce the appropriate syntax to use for includes.
#
#SETMAKE='MAKE = ${MAKE}' # define if make does not setup $MAKE
#
# General system stuff used by the distribution.
#
#CHMOD="/etc/chmod" # pathname of suitable chmod program
#INSTALL='${SHELL} ${PORT}/install.sh' # SGI install program/emulator
#LN="/bin/ln" # pathname of suitable ln program
#LN_S="-s" # option to ${LN} to create symlink
#MV_F="-f" # option to ${MV} to force operation
#SED="/bin/sed" # pathname of suitable sed program
#SCRIPT_SH="/bin/sh" # pathname of suitable shell
#STRIP="/bin/strip" # strip program used by install.sh
END-QUOTE
So, OK, now I have a good suspicion what program wrote it. If "#" has the
usual meaning, this file will do absolutely nothing -- every line is a comment.
>Hope this helps.
Me too. So far I'm stumped.
>David
David A. Cobb, Software Engineer, Public Access Advocate, All around nice guy.
Get my PGP key at
:<http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=superbiskit>
Fingerprint=0x{6E3E_DB8C_2E8C_4248_62B2_FE29_08EE_CF0A_3629_E954}
:<http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=superbiskit&fingerprint=on>
"By God's Grace I am a Christian man, by my actions a great sinner."
--The Way of a Pilgrim, R. M. French [tr.]
Potentially Viral Software is any software for which you are not allowed
to examine the source. Do not buy or use Potentially Viral Software!
<---.----!----.----!----.----!----.----!----.----!----.----!----.---->
- 2 participants
- 1 comments
c-mode is broken
22 years, 8 months
Alex Katebi
Alex Katebi
Hi folks,
In xemacs-21.4.4, system Solaris 2.7
When in c-mode, backsapce key or delete key do not
rub to the left. They act like ctl-d, which rubs to the right.
Can anyone tell me what I need to do to fix this.
Or is this a new bug?
Regards,
Alex Katebi
___________________________________________________________________________
Visit http://www.visto.com.
Find out how companies are linking mobile users to the
enterprise with Visto.
- 1 participants
- 0 comments
Selecting old grep command from menu broken
22 years, 8 months
eric dahlman
eric dahlman
This bug report will be sent to the XEmacs Development Team,
not to your local site managers!!
Please write in English, because the XEmacs maintainers do not have
translators to read other languages for them.
In XEmacs 21.5 (beta1) "anise" [Lucid] (sparc-sun-solaris2.8) of Fri Jun 22 2001 on sibelius
configured using `configure --prefix=/s/chopin/d/proj/meps/common/'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
Using tools->grep->grep... I ran the following grep command
find . -name "*.lisp" | xargs grep -n -i make-trace-filter
Which worked just fine. I changed to a difference directory and
attempted to rerun the command which had been added to the menu via
tools->grep->...ame "*.lisp" | xargs grep -n -i make-trace-filter
However, the elided command was run instead of the original resulting
in a failure to find the program "...ame"
-Eric
Recent keystrokes:
i n d . SPC - n a m e SPC " * . l i s p " SPC left
left left left left left left left left left left left
left left left left left SPC right right right right
right right right right right right right right right
right right right right | SPC right left x a r g s
SPC right right right right right right right SPC -
i SPC m a k e - t r a c e - f i l t e r RET misc-user
misc-user misc-user up RET misc-user
Recent messages (most recent first):
Composing a message...
Loading mh-comp...done
Loading mh-comp...
package specification is `common-lisp-user'
File mode specification error: (error "malformed -*- line")
Making completion list...
package specification is `common-lisp-user'
Wrote /s/chopin/d/proj/meps/eric/junk/test/pcl-error.lisp
package specification is `common-lisp-user'
Wrote /s/chopin/d/proj/meps/eric/junk/nasa-july30-2001/apex/loader.lisp
- 1 participants
- 0 comments
[PATCH] configure.usage fix
22 years, 8 months
Peter Brown
Peter Brown
Added option description that are checked for in configure but not listed in configure.usage.
not sure these need to get added so im not going to be cross if this patch doesnt get included
xemacs-21.4 Patch (cvs -f -z3 diff -u):
? confdefs.h
? configure.usage.new
? usage.diff
? lib-src/make-dump-id
cvs server: Diffing .
Index: configure.usage
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/configure.usage,v
retrieving revision 1.19.2.1
diff -u -r1.19.2.1 configure.usage
--- configure.usage 2001/07/25 07:39:23 1.19.2.1
+++ configure.usage 2001/07/31 19:09:39
＠＠ -77,15 +77,15 ＠＠
*WARNING* The Motif menubar is currently broken.
--with-scrollbars=TYPE Use TYPE scrollbars
(lucid, motif, athena, or no).
---with-dialogs=TYPE Use TYPE dialog boxes (motif, athena, or no).
+--with-dialogs=TYPE Use TYPE dialog boxes (lucid, motif, athena, or no).
Lucid menubars and scrollbars are the default.
Motif dialog boxes will be used if Motif can be found.
---with-widgets=TYPE Use TYPE widgets (motif, athena, or no).
+--with-widgets=TYPE Use TYPE widgets (lucid, motif, athena, or no).
Motif widgets will be used if Motif can be found.
Other widget types are currently unsupported.
--with-dragndrop Compile in the generic drag and drop API. This is
automatically added if one of the drag and drop
- protocols is found (currently CDE, OffiX, MSWindows).
+ protocols is found (currently CDE, OffiX, MSWindows, and GTK).
*WARNING* The Drag'n'drop support is under development
and is considered experimental.
--with-cde Compile in support for CDE drag and drop.
＠＠ -155,7 +155,7 ＠＠
--mail-locking=TYPE (*) Specify the locking to be used by movemail to prevent
concurrent updates of mail spool files. Valid types
- are `lockf', `flock', and `dot'.
+ are `lockf', `flock', `dot', `locking' or `mmdf'.
--with-pop Support POP for mail retrieval.
--with-kerberos Support Kerberos-authenticated POP.
--with-hesiod Support Hesiod to get the POP server host.
cvs server: Diffing dynodump
cvs server: Diffing dynodump/i386
cvs server: Diffing dynodump/ppc
cvs server: Diffing dynodump/sparc
cvs server: Diffing etc
cvs server: Diffing etc/custom
cvs server: Diffing etc/custom/example-themes
cvs server: Diffing etc/eos
cvs server: Diffing etc/idd
cvs server: Diffing etc/photos
cvs server: Diffing etc/sparcworks
cvs server: Diffing etc/tests
cvs server: Diffing etc/tests/external-widget
cvs server: Diffing etc/toolbar
cvs server: Diffing info
cvs server: Diffing lib-src
cvs server: Diffing lisp
cvs server: Diffing lisp/mule
cvs server: Diffing lisp/term
cvs server: Diffing lock
cvs server: Diffing lwlib
cvs server: Diffing man
cvs server: Diffing man/internals
cvs server: Diffing man/lispref
cvs server: Diffing man/new-users-guide
cvs server: Diffing man/xemacs
cvs server: Diffing modules
cvs server: Diffing modules/base64
cvs server: Diffing modules/ldap
cvs server: Diffing modules/sample
cvs server: Diffing modules/zlib
cvs server: Diffing netinstall
cvs server: Diffing nt
cvs server: Diffing nt/installer
cvs server: Diffing nt/installer/Wise
cvs server: Diffing src
cvs server: Diffing src/m
cvs server: Diffing src/s
cvs server: Diffing tests
cvs server: Diffing tests/DLL
cvs server: Diffing tests/Dnd
cvs server: Diffing tests/automated
cvs server: Diffing tests/gtk
cvs server: Diffing tests/mule
cvs server: Diffing tests/tooltalk
- 2 participants
- 2 comments
[ANNOUNCE] Updated Packages in Pre-Release - July 28
22 years, 8 months
Steve Youngs
Steve Youngs
Hey there everyone.
I have just added the following packages to the 'Pre-Releases'
directory:
New Packages in Pre-Release:
===========================
speedbar-1.21-pkg.tar.gz
vm-6.95-pkg.tar.gz
zenirc-1.11-pkg.tar.gz
Previously Announced Packages Still in Pre-Release:
==================================================
None
Detailed Changes:
================
speedbar-1.21-pkg.tar.gz
------------------------
2001-07-26 Charles G Waldman <cgw(a)xemacs.org>
* speedbar.texi: Correct spelling.
vm-6.95-pkg.tar.gz
------------------
2001-07-26 Steve Youngs <youngs(a)xemacs.org>
* Sync with VM-6.95.
zenirc-1.11-pkg.tar.gz
----------------------
2001-07-23 Adrian Aichner <adrian(a)xemacs.org>
* zenirc.el (zenirc-font-lock-keywords): Include last character
before > in fontification of font-lock-keyword-face. Use OVERRIDE
flag where appropriate to refine fontification.
Installing These:
================
Manually:
--------
1) Download the packages that you want to install from:
/ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/
2) Unpack them to: [1]
/usr/local/lib/xemacs/xemacs-packages/
3) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.[245].x):
----------------------------------------------
1) Tools -> Packages -> Add Download Site -> Pre-Releases
2) Tools -> Packages -> List and Install
3) Select the packages you wish to install (there are brief
instructions at the bottom of the packages buffer).
4) Packages -> Install/Remove Selected
5) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.1.14):
-------------------------------------------
1) Options -> Manage Packages -> Add Download Site -> Pre-Releases
2) Options -> Manage Packages -> List and Install
3 - 5) As per XEmacs 21.[245].x.
Footnotes:
[1] Note: Mule packages should be installed into:
/usr/local/lib/xemacs/mule-packages/
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
- 7 participants
- 12 comments