May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Hrvoje Niksic

Will someone please update lisp/README? I would gladly do so, but I know next to nothing about the package and load-path searching details. Or, am I the only one who cares about the random README's being up-to-date? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- The Lord protects children and fools... But don't push it.

1 participants
0 comments

Re: info.el should use easymenu 26 years, 6 months

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > > > SL Baur <steve(a)xemacs.org> writes: > >> * info.el (Info-mode): Use easymenu. > > > Is easy menu the offical XEmacs menu interface now? > > Yup. Hey! Since when? Easymenu is an undocumented hack. add-submenu and add-menu-button are the only Right, Documented Interfaces. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- I'm a Lisp variable -- bind me!

2 participants
1 comments

Re: Startup speed: Still too many stats? 26 years, 6 months

Hrvoje Niksic

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > Note this has nothing to do with packages. It's just core Lisp > which is causing the problem. You are right. Here is an analysis: * 20 stats related to various stuff, like binaries, /var/mail, etc; * 59 stats related to packages (basically stat-ing directories in my package path); * 331 stats related to lisp/ directory, stat-ing every file in the core lisp dir; * 26 more random stats searching for info directories, lib-src, `etc', and so on; * 59 stats related to auto-autoloads. These are obviously unavoidable and negligible, since the main overhead is probably in loading the files, anyway; * 84 stats related to searching for site-start{,.el,.elc}; * 80 stats related to searching for term/xterm{,.el,.elc} Total: 659 The optimization fodder are the 331 stats due to term/, 84 stats looking for site-start and 80 stats looking for xterm (or whatever terminal type). If these 495 stats could be removed, we would be left with 164 stats, which is well within the ballpark of 20.3 (102 stats) and FSF Emacs (95 stats, but much less directories) and better than 20.2 (245 stats). -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- The end of the world is coming... SAVE YOUR BUFFERS!

1 participants
0 comments

[comp.emacs.xemacs] Re: Changed RMAIL behavior 26 years, 6 months

Hrvoje Niksic

Should we do what Robert did? If that will make our old RMAIL users happy, why not? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Speak softly and carry a +6 two-handed sword. ------- Start of forwarded message ------- Newsgroups: comp.emacs.xemacs From: Perdita Stevens <Perdita.Stevens(a)dcs.ed.ac.uk> Subject: Re: Changed RMAIL behavior Message-ID: <e5c7m3r5s2j.fsf(a)shillay.dcs.ed.ac.uk> To: rhuff(a)cybercom.net Organization: Department of Computer Science, Edinburgh University References: <354A820B.A9946D0A(a)cybercom.net> Date: Tue, 12 May 1998 17:15:16 GMT Robert Huff <rhuff(a)cybercom.net> writes: > I just upgraded to Xemacs 20.2 from 19.4 (I think) ... and RMAIL > has changed drastically. I want the old behavior back - where do > I find information on all the new "functionality" and how to > disable it? I haven't found a better solution than to use an rmail.el from an old XEmacs (in my case, 19.16) instead of the horribly broken one that comes with 20.4. In the long run, we all have to "upgrade" to a supported mail-reader, I guess. (But don't think I haven't tried...) Perdita ------- End of forwarded message -------

1 participants
0 comments

Re: Basic package question 26 years, 6 months

Michael Sperber

>>>>> "Andy" == Andy Piper <andyp(a)parallax.co.uk> writes: Andy> At 04:15 PM 5/12/98 +0200, Michael Sperber [Mr. Preprocessor] wrote: Andy> ./configure --package-path=<some colon separated list of paths> >> >> By default, it's supposed to live under <root>/lib/xemacs/xemacs-packages. Andy> So if you don't specify things to configure packages will go there? Yes. >> Cheers =8-} Chipsy >> Friede, Völkerverständigung und überhaupt blabla Andy> I always wanted to know what this means. Literally: Peace, Universal International Understanding, Cooperation, Free Love, and To All A Good Night Amen. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

[Failure] 21.0 b39 on i686-pc-linux 26 years, 6 months

Raymond Toy

>From the full b39 tarballs and latest packages, b39 builds fine but crashes on startup. The initial window comes up, I can do some simple stuff, but after a timeout of a couple of seconds, it crashes. gdb says: (gdb) run -vanilla Starting program: /opt/XEmacs/bin/xemacs-21.0-b39 -vanilla Fatal error: assertion failed, file window.h, line 298, RECORD_TYPEP (_obj, lrecord_window) || MARKED_RECORD_P (_obj) Program received signal SIGABRT, Aborted. 0x402249e9 in __kill () (gdb) bt #0 0x402249e9 in __kill () #1 0x40260775 in gsignal () #2 0x8151d01 in Fredisplay_echo_area () at window.h:298 #3 0x80a9a0a in funcall_recording_as (recorded_as=-1473206540, nargs=0, args=0xbfffec04) at eval.c:3197 #4 0x80a9bd1 in Ffuncall (nargs=1, args=0xbfffec04) at eval.c:3238 #5 0x80852ee in Fbyte_code (bytestr=1747263036, vector=-2010833292, maxdepth=5) at bytecode.c:416 #6 0x80aa8c7 in funcall_lambda (fun=673521376, nargs=3, arg_vector=0xbfffedb8) at eval.c:3597 #7 0x80a9b95 in funcall_recording_as (recorded_as=-1472431284, nargs=3, args=0xbfffedb4) at eval.c:3214 #8 0x80a9bd1 in Ffuncall (nargs=4, args=0xbfffedb4) at eval.c:3238 #9 0x80852ee in Fbyte_code (bytestr=1747262888, vector=-2010833444, maxdepth=4) at bytecode.c:416 #10 0x80aa8c7 in funcall_lambda (fun=673521152, nargs=4, arg_vector=0xbfffef08) at eval.c:3597 #11 0x80a9b95 in funcall_recording_as (recorded_as=-1473209236, nargs=4, args=0xbfffef04) at eval.c:3214 #12 0x80a9bd1 in Ffuncall (nargs=5, args=0xbfffef04) at eval.c:3238 #13 0x80852ee in Fbyte_code (bytestr=1747263268, vector=-2010833088, maxdepth=5) at bytecode.c:416 #14 0x80aa8c7 in funcall_lambda (fun=673521504, nargs=2, arg_vector=0xbffff03c) at eval.c:3597 #15 0x80a9b95 in funcall_recording_as (recorded_as=-1473209188, nargs=2, args=0xbffff038) at eval.c:3214 #16 0x80a9bd1 in Ffuncall (nargs=3, args=0xbffff038) at eval.c:3238 #17 0x80852ee in Fbyte_code (bytestr=1747547432, vector=-2010548932, maxdepth=3) at bytecode.c:416 #18 0x80aa8c7 in funcall_lambda (fun=673805652, nargs=1, arg_vector=0xbffff9f8) at eval.c:3597 #19 0x80a9b95 in funcall_recording_as (recorded_as=-1472287732, nargs=1, args=0xbffff9f4) at eval.c:3214 #20 0x80a9bd1 in Ffuncall (nargs=2, args=0xbffff9f4) at eval.c:3238 #21 0x80852ee in Fbyte_code (bytestr=1747547784, vector=-2010548032, maxdepth=5) at bytecode.c:416 #22 0x80aa8c7 in funcall_lambda (fun=673806900, nargs=1, arg_vector=0xbffffb0c) at eval.c:3597 #23 0x80a9b95 in funcall_recording_as (recorded_as=-1472287684, nargs=1, args=0xbffffb08) at eval.c:3214 #24 0x80a9bd1 in Ffuncall (nargs=2, args=0xbffffb08) at eval.c:3238 #25 0x80aade3 in call1 (fn=-1472287684, arg0=674532260) at eval.c:3912 #26 0x80da040 in execute_internal_event (event=674532260) at event-stream.c:2930 #27 0x80ddd22 in Fdispatch_event (event=674532260) at event-stream.c:4667 #28 0x808c790 in Fcommand_loop_1 () at cmdloop.c:579 #29 0x808c49b in command_loop_1 (dummy=-1473314812) at cmdloop.c:494 #30 0x80a7614 in condition_case_1 (handlers=-1473314716, bfun=0x808c430 <command_loop_1>, barg=-1473314812, hfun=0x808b8d8 <cmd_error>, harg=-1473314812) at eval.c:1653 #31 0x808b9b0 in command_loop_3 () at cmdloop.c:256 #32 0x808b9cc in command_loop_2 (dummy=-1473314812) at cmdloop.c:267 #33 0x80a72a4 in internal_catch (tag=-1473237140, func=0x808b9c4 <command_loop_2>, arg=-1473314812, threw=0x0) at eval.c:1328 #34 0x808bd6a in initial_command_loop (load_me=-1473314812) at cmdloop.c:305 #35 0x80a3f55 in xemacs_21_0_b39_i686_pc_linux (argc=2, argv=0xbffffd3c, envp=0xbffffd48, restart=0) at emacs.c:1676 #36 0x80a45f8 in main (argc=2, argv=0xbffffd3c, envp=0xbffffd48) at emacs.c:2093 #37 0x8074bfb in _start () Installation file is: uname -a: Linux pc689 2.0.30 #1 Tue Apr 22 10:49:45 EDT 1997 i686 unknown ./configure '--prefix=/opt/XEmacs' XEmacs 21.0-b39 "Russian White" configured for `i686-pc-linux'. Where should the build process find the source code? /app1/src/xemacs-21.0-b39 What installation prefix should install use? /opt/XEmacs What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O2 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for X-Face message headers. Compiling in support for JPEG image conversion. Compiling in support for TIFF image conversion. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for OffiX. Compiling in support for Drag'n'Drop ( OffiX ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: ---------------------------------------------------------

2 participants
1 comments

vertical divider ... what a team we have ;-) 26 years, 6 months

Didier Verna

The vertical divider shadow thickness specifier is ready. I just have to patch mouse.el to make it look pressed when we drag it, and that's the "end of the game"[1]. I have to go now, so I'll do this tomorrow morning. Bye ! Footnotes: [1] Bonus point for the one who gives me the name of this song's author. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

[mail-lib] browser-url.el is old 26 years, 6 months

SAKIYAMA Nobuo

browser-url.el in mail-lib package is older than the author's version. THe latet version is available from http://wombat.doc.ic.ac.uk/emacs/browse-url.el -- SAKIYAMA Nobuo nobuo(a)db3.so-net.or.jp

1 participants
0 comments

Re: [Success] 21.0 "Saanen-pre2" XEmacs Lucid (beta40) on i386-pc-cyg win32 26 years, 6 months

Didier Verna

Mike Hill <mikehill(a)hgeng.com> writes: > Sorry if some of you have seen this already. It bounced back from > xemacs-build-reports, so I guess I'm not correctly subscribed. You don't need to.

1 participants
0 comments

[Success] 21.0 "Saanen-pre2" XEmacs Lucid (beta40) on i386-pc-cyg win32 26 years, 6 months

Michael Hill

Sorry if some of you have seen this already. It bounced back from xemacs-build-reports, so I guess I'm not correctly subscribed. Built and installed smoothly. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /binary/xemacs-21.0-b39/Installation: > (Output from most recent run of ./configure) uname -a: CYGWIN32_NT DILBERT 4.0 19.1 i686 unknown ./configure '--site-includes=/usr/local/include' XEmacs 21.0-b40 "Saanen-pre2" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /binary/xemacs-21.0-b39 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/cygwin32.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O2 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? default What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6.3/include Where do we find X Windows libraries? /usr/X11R6.3/lib Additional header files: /usr/local/include Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in File coding support. Compiling in support for OffiX. Compiling in support for Drag'n'Drop ( OffiX ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- > /binary/xemacs-21.0-b39/beta.err does not exist!

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta May 1998