April 1998 - XEmacs-Beta - XEmacs Mailing List Archives

[Success] 21.0 "Pygmy-pre1" XEmacs Lucid (beta37) on hppa1.1-hp-hpux11.00 26 years, 7 months

Marcus Thiessel

... with png support. BTW, did someone build a beta with socks support recently!? I downloaded socks but had trouble building socks itself and XEmacs. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /opt/src/xemacs-21.0-b36/Installation: > (Output from most recent run of ./configure) uname -a: HP-UX tmbbwtx B.11.00 A 9000/720 16954192 two-user license ./configure 'hppa1.1-hp-hpux11.00' '--dynamic=no' '--prefix=/usr/local/xemacs' '--with-x' '--with-dialogs=motif' '--with-xface=yes' '--with-tty=yes' '--x-includes=/usr/include/Motif1.2_R6 -I/usr/include/X11R6' '--x-libraries=/usr/lib/Motif1.2_R6 -L/usr/lib/X11R6' '--with-database=dbm' '--with-pop' '--mail-locking=lockf' '--site-includes=/usr/contrib/include -I/usr/local/include' '--error-checking=none' '--extra-verbose' '--site-libraries=/usr/contrib/lib -L/usr/local/lib' '--with-sound=no' '--with-xmu' '--with-mule=yes' '--with-cde=yes' '--with-session' '--with-tooltalk=yes' '--with-gcc=no' '--with-gnu-make=no' '--gung-ho' '--package-path=/opt/src/packages' '--cflags=+DA1.1 +DD32 +O2 +Onolimit +Odataprefetch +Oentrysched +Oprocelim +Olibcalls' XEmacs 21.0-b37 "Pygmy-pre1" configured for `hppa1.1-hp-hpux11.00'. Where should the build process find the source code? /opt/src/xemacs-21.0-b36 What installation prefix should install use? /usr/local/xemacs What operating system and machine description files should XEmacs use? `s/hpux11.h' and `m/hp800.h' What compiler should XEmacs be built with? cc -Ae +DA1.1 +DD32 +O2 +Onolimit +Odataprefetch +Oentrysched +Oprocelim +Olibcalls 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/dt/include /usr/include/Motif1.2_R6 -I/usr/include/X11R6 /usr/contrib/X11R6/include Where do we find X Windows libraries? /usr/dt/lib /usr/lib/Motif1.2_R6 -L/usr/lib/X11R6 /usr/contrib/X11R6/lib Additional header files: /usr/contrib/include -I/usr/local/include Additional libraries: /usr/contrib/lib -L/usr/local/lib 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 PNG image conversion. Compiling in support for DBM. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using Motif to provide XIM support. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "lockf" for locking mail spool files. Using POP for mail access Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. --Marcus

1 participants
0 comments

Re: coding-system lossage with eterm 26 years, 7 months

SL Baur

Glynn Clements <glynn(a)sensei.co.uk> writes: > I installed eterm-1.04, and noticed that the CR characters are being > eaten without eterm actually doing a carriage return, resulting in the > `staircase effect'. Verified. Note that the newest version of eterm has ANSI color support (color ls works, although the effect is lost in the ugliness of the staircase). > Using (setq process-coding-system-alist '((".*" . binary))) fixed the > problem, Does it? What happens if you cat a Japanese text file? I see something highly ugly and definitely not Japanese. > but it smells as if eterm is assuming that the coding system is > appropriate rather than making it so. Yup. > Is this MULE-related? I'm pretty sure. As far as I know, eterm has never been MULE-ized. Could someone knowledgeable please do up an appropriate patch? > Did anyone actually test eterm-1.04 on a MULE XEmacs? Is this a rhetorical question? :-)

4 participants
8 comments

[Success+shadowings] 21.0 "Pygmy-pre1" XEmacs Lucid (beta37) on sparc-sun-solaris2.5.1 26 years, 7 months

Oscar Figueiredo

2 shadowings: /logiciels/public/xemacs/lib/xemacs/packages/lisp/efs/passwd hides /logiciels/public/xemacs/lib/xemacs/packages/lisp/xemacs-base/passwd /logiciels/public/xemacs/lib/xemacs/packages/lisp/efs/auto-save hides /home/xemacs_dist/src/xemacs-21.0/lisp/auto-save 2 Emacs Lisp load-path shadowings were found passwd is in : efs-1.08-pkg.tar.gz and xemacs-base-1.18-pkg.tar.gz auto-save is in : efs-1.08-pkg.tar.gz and core lisp > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /logiciels/public/xemacs/src/xemacs-21.0/Installation: > (Output from most recent run of ./configure) uname -a: SunOS lspsun12 5.5.1 Generic_103640-08 sun4m sparc SUNW,SPARCstation-20 ./configure 'sparc-sun-solaris2.5.1' '--with-gcc=no' '--cflags=-g' '--site-includes=/usr/local/include /usr/local/include/X11 /logiciels/public/divers/include' '--site-libraries=/usr/local/lib /usr/local/lib/X11 /logiciels/public/divers/lib' '--dynamic' '--prefix=/logiciels/public/xemacs' '--with-workshop' '--with-cde' '--with-sound=native' '--with-mule=no' '--with-menubars=lucid' '--with-scrollbars=lucid' '--with-dialogs=motif' '--debug' '-error-checking=all' '--use-union-type' '--no-doc-file' XEmacs 21.0-b37 "Pygmy-pre1" configured for `sparc-sun-solaris2.5.1'. Where should the build process find the source code? /logiciels/public/xemacs/src/xemacs-21.0 What installation prefix should install use? /logiciels/public/xemacs What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? cc -g 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/dt/include /usr/local/include Where do we find X Windows libraries? /usr/dt/lib /usr/local/lib Additional header files: /usr/local/include /usr/local/include/X11 /logiciels/public/divers/include Additional libraries: /usr/local/lib /usr/local/lib/X11 /logiciels/public/divers/lib Runtime library search path: /usr/local/lib:/logiciels/public/divers/lib:/usr/dt/lib:/opt/SUNWdt/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 PNG image conversion. Compiling in support for TIFF image conversion. Compiling in native sound support. Compiling in support for GNU DBM. Compiling in support for LDAP (UMich libs). Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in support for OffiX. Compiling in support for Sun WorkShop. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using the union type for Lisp_Objects. 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: --------------------------------------------------------- > /logiciels/public/xemacs/src/xemacs-21.0/beta.err does not exist!

1 participants
0 comments

Re: XEmacs-20.4; [Bug] char syntax `inherit' 26 years, 7 months

SL Baur

Ben Wing <ben(a)666.com> writes: > This is probably something that I messed up in the process of > emulating FSF Emacs. Oops. Um, what do we do to fix it?

1 participants
0 comments

Re: coding-system lossage with eterm 26 years, 7 months

SL Baur

Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: > The default should be a defcustom, probably defaulted to ISO-8859-1. > When possible, the coding system should be set according to LANG. > (Steve, were you running with LANG=ja or not? I gotta get some sleep, > so I'm not going to experiment further....) No, let me try it again ... same result -- staircase mojibake.

2 participants
1 comments

[Crash] 21.0b37pre1: print-message-label 26 years, 7 months

Oscar Figueiredo

I can't launch XEmacs 21.0b37pre1. It's the first time I configure with --gung-ho, I don't know if it's related, I am trying to recompile without. Fatal error (4). [...] Lisp backtrace follows: # bind (print-message-label) display-error((wrong-type-argument stringp [1] Illegal instruction src/xemacs -q -no-site-file (core dumped) C Backtrace: Current function is print_internal 1203 (obj, printcharfun, escapeflag)); (dbx) where [1] 0x5618e4(0xefffe0c0, 0xefffe0bc, 0x1, 0xefffe234, 0x4, 0x4), at 0x5618e3 =>[2] print_internal(obj = UNION, printcharfun = UNION, escapeflag = 1), line 1203 in "print.c" [3] print_cons(obj = UNION, printcharfun = UNION, escapeflag = 1), line 904 in "print.c" [4] print_internal(obj = UNION, printcharfun = UNION, escapeflag = 1), line 1203 in "print.c" [5] Fprin1(object = UNION, stream = UNION), line 502 in "print.c" [6] Fbacktrace(stream = UNION, detailed = UNION), line 4927 in "eval.c" [7] fatal_error_signal(sig = 4), line 243 in "emacs.c" ---- called from signal handler with signal 4 (SIGILL) ------ [8] 0x5618e4(), at 0x5618e3 [9] Fprin1(object = UNION, stream = UNION), line 502 in "print.c" [10] print_error_message(error_object = UNION, stream = UNION), line 669 in "print.c" [11] Fdisplay_error(error_object = UNION, stream = UNION), line 700 in "print.c" [12] funcall_recording_as(recorded_as = UNION, nargs = 2, args = 0xefffef58), line 3197 in "eval.c" [13] Ffuncall(nargs = 3, args = 0xefffef58), line 3238 in "eval.c" [14] Fbyte_code(bytestr = UNION, vector = UNION, maxdepth = UNION), line 416 in "bytecode.c" [15] funcall_lambda(fun = UNION, nargs = 1, arg_vector = 0xeffff35c), line 3599 in "eval.c" [16] funcall_recording_as(recorded_as = UNION, nargs = 1, args = 0xeffff358), line 3200 in "eval.c" [17] Ffuncall(nargs = 2, args = 0xeffff358), line 3238 in "eval.c" [18] call1(fn = UNION, arg0 = UNION), line 3912 in "eval.c" [19] cmd_error(data = UNION, dummy = UNION), line 195 in "cmdloop.c" [20] condition_case_1(handlers = UNION, bfun = 0x11b2c0 = &Feval(Lisp_Object form), barg = UNION, hfun = 0xb3c88 = &`xemacs`cmdloop.c`cmd_error(Lisp_Object data, Lisp_Object dummy), harg = UNION), line 1636 in "eval.c" [21] top_level_1(dummy = UNION), line 206 in "cmdloop.c" [22] internal_catch(tag = UNION, func = 0xb3da8 = &`xemacs`cmdloop.c`top_level_1(Lisp_Object dummy), arg = UNION, threw = (nil)), line 1328 in "eval.c" [23] initial_command_loop(load_me = UNION), line 285 in "cmdloop.c" [24] xemacs_21_0_b37_sparc_sun_solaris2_5_1(argc = 3, argv = 0xeffff84c, envp = 0xeffff85c, restart = 0), line 1669 in "emacs.c" [25] main(argc = 3, argv = 0xeffff84c, envp = 0xeffff85c), line 2086 in "emacs.c" Configuration : uname -a: SunOS lspsun12 5.5.1 Generic_103640-08 sun4m sparc SUNW,SPARCstation-20 ./configure 'sparc-sun-solaris2.5.1' '--with-gcc=no' '--cflags=-g' '--site-includes=/usr/local/include /usr/local/include/X11 /logiciels/public/divers/include' '--site-libraries=/usr/local/lib /usr/local/lib/X11 /logiciels/public/divers/lib' '--dynamic' '--prefix=/logiciels/public/xemacs' '--with-workshop' '--with-cde' '--with-sound=native' '--with-mule=no' '--with-menubars=lucid' '--with-scrollbars=lucid' '--with-dialogs=motif' '--debug' '-error-checking=all' '--use-union-type' '--gung-ho' '--no-doc-file' XEmacs 21.0-b37 "Pygmy-pre1" configured for `sparc-sun-solaris2.5.1'. Where should the build process find the source code? /logiciels/public/xemacs/src/xemacs-21.0 What installation prefix should install use? /logiciels/public/xemacs What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? cc -g 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/dt/include /usr/local/include Where do we find X Windows libraries? /usr/dt/lib /usr/local/lib Additional header files: /usr/local/include /usr/local/include/X11 /logiciels/public/divers/include Additional libraries: /usr/local/lib /usr/local/lib/X11 /logiciels/public/divers/lib Runtime library search path: /usr/local/lib:/logiciels/public/divers/lib:/usr/dt/lib:/opt/SUNWdt/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 PNG image conversion. Compiling in support for TIFF image conversion. Compiling in native sound support. Compiling in support for GNU DBM. Compiling in support for LDAP (UMich libs). Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in support for OffiX. Compiling in support for Sun WorkShop. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using the union type for Lisp_Objects. 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: ---------------------------------------------------------

1 participants
0 comments

Re: [Failure '--external-widget=yes'] XEmacs 21.0-b37 "Pygmy-pre1", sparc-sun-solaris2.5.1 26 years, 7 months

SL Baur

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > Building (from CVS) with > '--external-widget=yes' > leads: > "frame-x.c", line 2502: undefined symbol: popup As near as I can tell from examining old versions of this function, that test is dead code which should be deleted (this is why I didn't apply your proposed patch for this earlier). 1998-04-23 SL Baur <steve(a)altair.xemacs.org> * frame-x.c (x_delete_frame): remove dead code. Index: src/frame-x.c =================================================================== RCS file: /usr/local/xemacs/xemacs-20.0/src/frame-x.c,v retrieving revision 1.30 diff -u -r1.30 frame-x.c --- src/frame-x.c 1998/04/07 05:39:41 1.30 +++ src/frame-x.c 1998/04/24 05:38:26 ＠＠ -2499,8 +2499,7 ＠＠ XtUnrealizeWidget() here. Xt can really suck. */ if (f->being_deleted) XtUnrealizeWidget (w); - if (NILP (popup)) - XtDestroyWidget (w); + XtDestroyWidget (w); x_error_occurred_p (dpy); } #else O.K. This goes on to bomb later: pgcc -c -fpic -g -fno-exceptions -Demacs -I. -DHAVE_CONFIG_H -I/usr/X11/include /home/xemacs/xemacs-20.0/src/ExternalClient.c mv ExternalClient.o ExternalClient-Xt-shared.o pgcc -c -fpic -g -fno-exceptions -Demacs -I. -DHAVE_CONFIG_H -I/usr/X11/include /home/xemacs/xemacs-20.0/src/extw-Xt.c mv extw-Xt.o extw-Xt-shared.o pgcc -c -fpic -g -fno-exceptions -Demacs -I. -DHAVE_CONFIG_H -I/usr/X11/include /home/xemacs/xemacs-20.0/src/extw-Xlib.c mv extw-Xlib.o extw-Xlib-shared.o EXTW_LINK(ExternalClient-Xt-shared.o extw-Xt-shared.o extw-Xlib-shared.o, libextcli_Xt.so.1) zsh: command not found: EXTW_LINK make[1]: *** [libextcli_Xt.so.1] Error 1 make[1]: Leaving directory `/usr/src/build20/external-widget/src' make: *** [src] Error 2 Now what?

1 participants
0 comments

Re: "X-Mailing-List:" 26 years, 7 months

Jason R Mastaler

Kazuyoshi Furutaka <furutaka(a)tokai.pnc.go.jp> writes: > I'd like the "X-Mailing-List:" header to be > "X-Mailing-List: <xemacs-beta(a)xemacs.org> archive/latest/28XXX" > rather than > "X-Mailing-List: <xemacs-beta(a)xemacs.org>". > With the latter form, it is difficult to sort and trace threads... Unfortunately, you'll have the live with the new format. The first is a feature of the SmartList MLM which we are no longer using. Sorry.

1 participants
0 comments

Re: [SUCCESS] 21.0 "Pygmy-pre1" XEmacs Lucid (beta37) on i586-pc-linux 26 years, 7 months

SL Baur

Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes: >>>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: Stephen> However, according my understanding of something Steve Baur wrote, it Stephen> should be possible to run XEmacs with _nothing_ except the binary Stephen> itself, and at least manage the functionality of MS-Edit under DOS. Stephen> If that is a goal, then crashing just because it can't find any Stephen> packages, or even core Lisp, is not acceptable. Steve? That is correct. With just the core lisp, it's still better than VI, I believe. > Right. This has little to do with path searching, but I have a set of > patches that make it go a lot further than it did. Still, it's very > much hardwired into the system that it can get at the core Lisp > auto-autoloads. Questions for Steve: > - Is being able to run a naked executable a priority? Yes. Jamie Zawinski and others run XEmacs that way. You should be able to find the bitching about this on c.e.x in DejaNews. Another way to look at it though is to consider this a case of graceful degradation. We should still have warning messages, but if the user knows what he is doing, he should be able to do it. > - What's the rationale of auto-autoloads not being dumped? There's two main reasons. You can't ensure that every package you ever wish to have around will be available at dump time. You want to be able to pick up[1] freshly installed packages the same way packages installed at dump time are picked up. You also want to be able to reload the autoloads of packages that have been upgraded.[2] This could be implemented by rescanning the autoloads at startup and reloading autoloads files that weren't present at dump time and reloading out of date autoloads. For a variety of reasons, I suspect this is much slower than just reloading all the autoloads to begin with. Also, there is no clean way we can unload files once they have been loaded. -More- If you happen to touch the timestamp of the installed binary you lose forever after. The easiest and safest way to ensure that all autoloaded stuffs are present and up-to-date is to load them in at run-time. I think loading autoloads at runtime is a win. I think as people gain experience with longer lived binaries (I don't see this happening too much while updates are being made every other day) they will appreciate this feature too. Think about it a second. It's another step in the direction of making the dumped binary less special. Stop XEmacs. Install a bunch of new lisp packages. Restart XEmacs. With the current architecture you are now in an identical situation to what used to require redumping the binary (or recompiling and relinking temacs if the object code is no longer available). The new lisp is bound as tightly to XEmacs as Lisp that was present at dump time. Footnotes: [1] "Pick up" means load the autoloads. [2] If you don't, we can perhaps work out some method of dumping autoloads and then ignoring new stuff in the future.

1 participants
0 comments

Re: Michael Harnois' problem with egcs/Mule 26 years, 7 months

Richard Ketchersid

I sent an almost identical report about getting segfaults in temacs last week, so Michael Harnois is not alone. I am using egcs-2.91.23, and glibc-2.1 ( 2.0.92 ). __________________ Richard Ketchersid +++_/_/+++_/_/++ UC Berkeley, Logic Group ++_/_/_/++_/+_/+ Office: 846 Evans +_/+++ _/+_/_/++ On Wed, 22 Apr 1998, Andreas Jaeger wrote: % % Hi, % % I'm trying to find out Michael's problem with current egcs snapshots % and current Mule-enabled XEmacsen. I do think we both have a similar % configuration (correct my Michael, if I'm wrong): quite recent egcs % 1.1 development version (in my case egcs-2.91.24 plus some patches), % glibc 2.1 development version and XEmacs development version. I know % that's too much - I don't really know whom to blame ;-). % % The problem shows up with a segmentation fault at build time: % make[1]: Entering directory `/mnt/xemacs/build-20.5/src' % EMACSBOOTSTRAPLOADPATH="/mnt/xemacs/cvs-sources/xemacs-20/src/../lisp/:/mnt/xemacs/build-20.5" ./temacs -batch -l /mnt/xemacs/cvs-sources/xemacs-20/src/../lisp/update-elc.el % make[1]: *** [update-elc.stamp] Segmentation fault % % running temacs under gdb I get: % Program received signal SIGSEGV, Segmentation fault. % 0x4028c4b9 in memcpy (dstpp=0x83ded04, srcpp=0x83debec, len=136122783) % at ../sysdeps/generic/memcpy.c:55 % (gdb) bt % #0 0x4028c4b9 in memcpy (dstpp=0x83ded04, srcpp=0x83debec, len=136122783) % at ../sysdeps/generic/memcpy.c:55 % #1 0x807dd12 in resize_string (s=0x83d917c, pos=194, delta=-136122589) % at /mnt/xemacs/cvs-sources/xemacs-20/src/alloc.c:2268 % #2 0x8082aff in set_string_char (s=0x83d917c, i=161, c=161) % at /mnt/xemacs/cvs-sources/xemacs-20/src/alloc.c:2329 % #3 0x8091e0d in complex_vars_of_casetab () % at /mnt/xemacs/cvs-sources/xemacs-20/src/casetab.c:323 % #4 0x80ad737 in xemacs_21_0_b36_i486_pc_linux (argc=5, argv=0xbffffa28, % envp=0xbffffa40, restart=0) % at /mnt/xemacs/cvs-sources/xemacs-20/src/emacs.c:1486 % #5 0x80af162 in main (argc=5, argv=0xbffffa28, envp=0xbffffa40) % at /mnt/xemacs/cvs-sources/xemacs-20/src/emacs.c:2019 % #6 0x40245d06 in __libc_start_main (main=0x80af100 <main>, argc=5, % argv=0xbffffa28, init=0x8079870 <_init>, fini=0x81cb4f0 <_fini>, % rtld_fini=0x4000a580 <_dl_fini>) at ../sysdeps/generic/libc-start.c:72 % % debugging into set_string_char I get: % % Breakpoint 3, set_string_char (s=0x83d917c, i=159, c=159) % at /mnt/xemacs/cvs-sources/xemacs-20/src/alloc.c:2328 % 3: bytoff = 190 % 2: newlen = 3 % 1: oldlen = 3 % Breakpoint 3, set_string_char (s=0x83d917c, i=160, c=160) % at /mnt/xemacs/cvs-sources/xemacs-20/src/alloc.c:2328 % 3: bytoff = 192 % 2: newlen = 3 % 1: oldlen = 4 % % And naturally the program fails since oldlen > newlen: % if (oldlen != newlen) % resize_string (s, bytoff, newlen - oldlen); % % Ok, what's so special about character 160 that it fails for this % single character? The glibc 2.1 test program for islower and friends % outputs the following characteristics: % 160/'\240' iscntrl; lower = 160/'\240'; upper = 160/'\240' % % Has anybody any ideas what's wrong? Why is oldlen > newlen? Any % ideas what I can check? % % Andreas %

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 April 1998