August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: No gutter visible under AIX / X11 25 years, 3 months

ALTMARK＠de.ibm.com

Michael, thank you for the offer of AFS access to a checked-out 21.2. This would of course be the easiest way for me to access the latest betas. Could you send me the cell name, DB server names (I don't think they're in our CellServDB) and the directory path? I'll also try (remote) CVS when I have enough time (-> means *never* ... ;-) ) to dig deeper into this stuff, although I really *did* say "firewall" and am aware that it might not be that easy to set up ... On the other hand, the tarballs are made available quite frequently (at least in my opinion), so for the moment I stick with them and wait for the next one - BTW: Does anybody know when b20 is planned to be released ...? :-) --- Markus Alt IBM Laboratory Boeblingen, Germany Workplace: 71032-19-171 sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) on 08/20/99 10:31:40 AM Please respond to sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) To: xemacs-beta(a)xemacs.org cc: (bcc: Markus Alt/Germany/IBM) Subject: Re: No gutter visible under AIX / X11 >>>>> "MA" == ALTMARK <ALTMARK(a)de.ibm.com> writes: MA> Thanks for the advice! I think, for the moment I'll stay with the tarballs MA> as setting up efs to use cvs seems to be not that simple for our MA> site Actually, this won't work at all, and isn't meant to be. You pretty much have to use remote CVS. I can offer AFS access to a checked-out 21.2 which is updated reasonably frequently. (Usually at least every beta.) -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Yeah! Using instructions missing from the README, xemacs installed! (was Re: How can xemacs have been made so hard to install? Do the developers have any clue it is needlessly hard/undocumented?) 25 years, 3 months

SL Baur

Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes in xemacs-beta(a)xemacs.org: > I do not understand why the SUMO tarball contains only packages. Because they are completely independent of XEmacs version and I want the same Sumo to be usable with both 21.2 and 21.1 (and InfoDock, for that matter). > I think it was a mistake to separate the executable from the packages > that way (SUMO lisp gets updated more frequently than the core tarball, > but it's not that much more so, and it's error-prone). That's reflecting a problem in how I build Sumos. I have intended to keep Lisp packages more frequently updated, but the expense of making new Sumos at the same time has been overwhelming. > It would be better if SUMO tarballs contained all of XEmacs. There currently isn't any way to build XEmacs completely from scratch, even for me. The Sumos aren't intended to support being bytecompiled. I am working on a method for building from scratch, but the hardest point right now is how to do this *and* maintain the current separation. As you should well know, the United States is not the world and in some countries telephone access is limited and extremely expensive and I have been catering and will continue to cater to those folks.

2 participants
1 comments

[Success with udp support] XEmacs 21.2-b19 "Shinjuku", i586-pc-win32 25 years, 3 months

Adrian Aichner

I am reporting a successful build on WinNT4sp4, VSC6.0, from CVS: cd d:\tmp\21.2\xemacs\ cvs -z3 update -P -d -r release-21-2 Compilation started at Fri Aug 20 10:08:57 1999 With following patch applied: > From: Stephen Tse <stephent(a)sfu.ca> > Subject: udp support > To: xemacs-patches(a)xemacs.org, eicq(a)aarg.net > Date: 19 Aug 1999 17:44:25 -0700 > Message-ID: <87672bjn6e.fsf(a)cr610941-a.rct1.bc.wave.home.com> It compiles and runs fine. Regards, Adrian > XEmacs Build Report as generated with > M-x build-report RET > by build-report-version $Revision: 1.3 $ follows: > Contents of d:\tmp\21.2\xemacs\Installation: > (Output from most recent run of ./configure) OS: Windows_NT XEmacs 21.2-b19 \"Shinjuku\" configured for `i586-pc-win32'. Building XEmacs in \"d:\\tmp\\21.2\\xemacs\\nt\". Using compiler \"cl -nologo -W3 -O2 -G5\". Installing XEmacs in \"c:\\XEmacs\\XEmacs-21.2-b19\". Package path is \"~\\.xemacs;;c:\\XEmacs\\site-packages;c:\\XEmacs\\xemacs-packages\". Compiling in support for Microsoft Windows native GUI. Compiling in support for XPM images. Compiling in support for GIF images. Compiling in support for PNG images. Compiling in support for TIFF images. Compiling in support for JPEG images. Compiling in support for X-Face message headers. Compiling in support for toolbars. Compiling in support for dialogs. Compiling in support for widgets. Compiling in support for native sounds. Compiling in fast dired implementation. Using minimal tagbits. Using indexed lrecord implementation. Using union type for Lisp object storage. > Contents of d:\tmp\21.2\xemacs\nt\xemacs-make-all-tse-udp.err > keeping lines matching > "^--\[\[\|\]\]$\|^$cd\|n?make$\s-\|errors?\|warnings?\|pure.*$space\|size$\|hides\b\|strange\|shadowings\|^Compil$ing\s-+in\|ation$\|^Using\|not\s-+found\|^While\s-+compiling.*$ \s-+.+$*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+" > and then deleting lines matching > "confl.*with.*auto-inlining" cd d:\tmp\21.2\xemacs\nt\ nmake /f xemacs.mak INSTALL_DIR="c:\XEmacs\XEmacs-$(XEMACS_VERSION_STRING)" PACKAGE_PREFIX="c:\XEmacs" HAVE_XPM="1" HAVE_PNG="1" HAVE_TIFF="1" HAVE_JPEG="1" HAVE_XFACE="1" USE_UNION_TYPE="1" GUNG_HO="1" COMPFACE_DIR="d:\tmp\libs4xemacs\compface" JPEG_DIR="d:\tmp\libs4xemacs\jpeg-6b" TIFF_DIR="d:\tmp\libs4xemacs\tiff-v3.4" ZLIB_DIR="d:\tmp\libs4xemacs\zlib" PNG_DIR="d:\tmp\libs4xemacs\libpng-1.0.2" XPM_DIR="d:\tmp\libs4xemacs\xpm-3.4k" all Compilation started at Fri Aug 20 10:40:48 1999 Installing XEmacs in \"c:\\XEmacs\\XEmacs-21.2-b19\". 1 file(s) copied. 1 file(s) copied. 1 file(s) copied. ..\lib-src/pop.c(925) : warning C4013: 'close' undefined; assuming extern returning int ..\lib-src\run.c(68) : warning C4101: 'j' : unreferenced local variable ..\lib-src\run.c(160) : warning C4101: 'tmp' : unreferenced local variable ..\src\event-msw.c(1965) : warning C4244: 'function' : conversion from 'long ' to 'unsigned short ', possible loss of data ..\src\event-msw.c(1978) : warning C4244: 'function' : conversion from 'long ' to 'unsigned short ', possible loss of data ..\src\event-msw.c(1965) : warning C4761: integral size mismatch in argument; conversion supplied ..\src\event-msw.c(1978) : warning C4761: integral size mismatch in argument; conversion supplied ..\src\glyphs-msw.c(2362) : warning C4133: ':' : incompatible types - from 'struct HICON__ *' to 'struct HBITMAP__ *' C:\Program Files\Microsoft Visual Studio\VC98\include\direct.h(132) : warning C4030: first formal parameter list longer than the second list ..\src\gif_io.c(118) : warning C4013: 'close' undefined; assuming extern returning int ..\src\alloc.c(1548) : warning C4244: '=' : conversion from 'long ' to 'unsigned short ', possible loss of data ..\src\data.c(777) : warning C4244: '=' : conversion from 'unsigned long ' to 'unsigned char ', possible loss of data ..\src\editfns.c(859) : warning C4013: 'getcwd' undefined; assuming extern returning int ..\src\editfns.c(859) : warning C4047: '=' : 'char *' differs in levels of indirection from 'int ' ..\src\filemode.c(82) : warning C4761: integral size mismatch in argument; conversion supplied ..\src\filemode.c(83) : warning C4761: integral size mismatch in argument; conversion supplied ..\src\filemode.c(84) : warning C4761: integral size mismatch in argument; conversion supplied ..\src\glyphs-eimage.c(923) : warning C4244: '=' : conversion from 'long ' to 'unsigned short ', possible loss of data ..\src\glyphs-eimage.c(924) : warning C4244: '=' : conversion from 'long ' to 'unsigned short ', possible loss of data ..\src\glyphs-eimage.c(925) : warning C4244: '=' : conversion from 'long ' to 'unsigned short ', possible loss of data ..\src\keymap.c(1065) : warning C4244: '=' : conversion from 'long ' to 'unsigned char ', possible loss of data ..\src\keymap.c(2081) : warning C4244: '=' : conversion from 'long ' to 'unsigned char ', possible loss of data ..\src\line-number.c(296) : warning C4146: unary minus operator applied to unsigned type, result still unsigned ..\src\nt.c(1611) : warning C4113: 'void (__cdecl *)()' differs in parameter lists from 'void (__cdecl *)(int )' ..\src\ntproc.c(752) : warning C4244: '=' : conversion from 'long ' to 'char ', possible loss of data ..\src\regex.c(2391) : warning C4244: '=' : conversion from 'long ' to 'char ', possible loss of data ..\src\unexnt.c(265) : warning C4028: formal parameter 2 different from declaration Using load-path (..\lisp ~\.xemacs c:\XEmacs\site-packages c:\XEmacs\xemacs-packages) Using module-load-path (..\modules) While compiling x-font-menu-font-data in file d:\tmp\21.2\xemacs\lisp\auto-autoloads.el: ** reference to free variable x-font-regexp-foundry-and-family ** reference to free variable x-font-regexp While compiling the end of the data: ** the function vassoc is not known to be defined. While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\toolbar-items.el: ** The following functions are not known to be defined: pending-delete-pre-hook, gnus, x-init-specifier-from-resources While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\dragdrop.el: ** the function mime/viewer-mode is not known to be defined. While compiling get-selection-no-error in file d:\tmp\21.2\xemacs\lisp\select.el: ** variable err bound but not referenced While compiling select-convert-to-class: ** reference to free variable x-emacs-application-class While compiling the end of the data: ** the function x-yank-clipboard-selection is not known to be defined. While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\mouse.el: ** the function x-store-cutbuffer is not known to be defined. While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\gui.el: ** The following functions are not known to be defined: set-annotation-action, set-annotation-data While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\coding.el: ** the function set-console-tty-coding-system is not known to be defined. While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\scrollbar.el: ** the function x-init-scrollbar-from-resources is not known to be defined. While compiling press-toolbar-button in file d:\tmp\21.2\xemacs\lisp\toolbar.el: ** reference to free variable toolbar-blank-press-function While compiling itimer-edit-mode in file d:\tmp\21.2\xemacs\lisp\itimer.el: ** buffer-flush-undo is an obsolete function; use buffer-disable-undo instead. While compiling nt-shell-mode-hook in file d:\tmp\21.2\xemacs\lisp\winnt.el: ** assignment to free variable comint-completion-addsuffix ** assignment to free variable comint-process-echoes While compiling find-space-insertable-point in file d:\tmp\21.2\xemacs\lisp\fill.el: ** reference to free variable space-insertable While compiling the end of the data: ** The following functions are not known to be defined: kinsoku-process-extend, kinsoku-process While compiling isearch-help-or-delete-char in file d:\tmp\21.2\xemacs\lisp\isearch-mode.el: ** reference to free variable tty-erase-char While compiling the end of the data: ** The following functions are not known to be defined: x-keysym-on-keyboard-sans-modifiers-p, x-get-selection, x-get-clipboard While compiling read-library-internal in file d:\tmp\21.2\xemacs\lisp\lib-complete.el: ** reference to free variable read-library-internal-search-path While compiling read-library-name: ** variable read-library-internal-search-path bound but not referenced While compiling set-visited-file-name in file d:\tmp\21.2\xemacs\lisp\files.el: ** reference to free variable vc-mode While compiling find-backup-file-name: ** variable bv-length bound but not referenced While compiling save-some-buffers-1: ** assignment to free variable view-exit-action While compiling the end of the data: ** The following functions are not known to be defined: vc-after-save, dired-get-filename, dired-expunge-deletions, ange-ftp-ftp-path While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\help.el: ** The following functions are not known to be defined: Info-find-node, compiled-function-annotation While compiling command-line-1 in file d:\tmp\21.2\xemacs\lisp\startup.el: ** variable first-file-buffer bound but not referenced While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\modeline.el: ** the function vc-toggle-read-only is not known to be defined. While compiling read-file-name-1 in file d:\tmp\21.2\xemacs\lisp\minibuf.el: ** reference to free variable rfhookfun While compiling mouse-read-file-name-1: ** reference to free variable rfhookfun While compiling the end of the data: ** The following functions are not known to be defined: ange-ftp-ftp-path, user-name-all-completions, user-name-completion-1, tty-color-list While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\simple.el: ** The following functions are not known to be defined: x-keysym-on-keyboard-sans-modifiers-p, kinsoku-process While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\frame.el: ** the function console-tty-controlling-process is not known to be defined. While compiling set-face-stipple in file d:\tmp\21.2\xemacs\lisp\faces.el: ** reference to free variable x-bitmap-file-path While compiling the end of the data: ** The following functions are not known to be defined: x-init-face-from-resources, x-init-device-faces, x-init-frame-faces, x-init-global-faces While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\console.el: ** the function console-tty-controlling-process is not known to be defined. While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\syntax.el: ** The following functions are not known to be defined: charset-name, char-charset While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\custom.el: ** the function custom-theme-reset-internal-face is not known to be defined. While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\cl-extra.el: ** The following functions are not known to be defined: overlay-lists, overlay-start, overlay-end, overlays-at, next-overlay-change While compiling paths-find-superlock-file in file d:\tmp\21.2\xemacs\lisp\setup-paths.el: ** reference to free variable configure-superlock-file Using load-path (..\lisp ~\.xemacs c:\XEmacs\site-packages c:\XEmacs\xemacs-packages) Using module-load-path (..\modules) Note: Strange doc (not fboundp) for function user-name-completion-1 ＠ 536478 Note: Strange doc (not fboundp) for function user-name-all-completions ＠ 536742 Note: Strange doc (not fboundp) for function make-symbolic-link ＠ 688289 Formatting: Assertions and Errors ... Formatting: Error Checking ... Formatting: Formatting Error Messages ... Formatting: ＠code{＠＠error＠{＠}} (＠error{}): Indicating an Error Message ... Formatting: Installing an Info File ... Formatting: Installing Info Directory Files ... Formatting: ＠code{makeinfo} Find Errors ... Formatting: Catching Errors with Info Formatting ... Formatting: Catching Errors with ＠TeX{} Formatting ... Formatting: Q2.0.1: Running XEmacs without installing ... Formatting: Q2.0.6: I'm having strange crashes. What do I do? ... Formatting: Q2.1.4: Startup warnings about deducing proper fonts? ... Formatting: Q2.1.10: Warnings from incorrect key modifiers. ... Formatting: Q2.1.11: ＠samp{Can't instantiate image error...} in toolbar ... Formatting: Q4.0.9: rmail or VM gets an error incorporating new mail. ... Formatting: Q4.7.4: Problems installing AUC TeX. ... Formatting: Q5.0.14: Strange things are happening in Shell Mode. ... Formatting: XEmacs and Installing Packages ... 1 file(s) copied. Reading included file: d:\tmp\21.2\xemacs\man\lispref\errors.texi Formatting: Error Messages ... Formatting: Errors ... Formatting: How to Signal an Error ... Formatting: How XEmacs Processes Errors ... Formatting: Writing Code to Handle Errors ... Formatting: Error Symbols and Condition Names ... Formatting: Entering the Debugger on an Error ... Formatting: Trapping Errors ... Formatting: Warnings ... Formatting: Standard Errors ... 1 file(s) copied. Formatting: Pure Space ... Compilation finished at Fri Aug 20 10:53:45

1 participants
0 comments

Re: xemacs source code HOWTO ? 25 years, 3 months

Michael Sperber

>>>>> "dv" == Didier Verna <verna(a)inf.enst.fr> writes: dv> Andy Piper <andy(a)xemacs.org> wrote: >> These are not useless. It means you can just change the header instead of >> all of your source code if your definition of how to access bar changes. dv> Yes, but I'd prefer being able to debug XEmacs, even if it costs me a dv> one-or-two-shot sed call on all sources to change "->foo" to "->bar" once in a dv> year (century ?). Well, the solution to that is to move more code into the substrate, rather than switching the implementation language to one of the three most fucked-up languages alive. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

3 participants
2 comments

Re: Building XEmacs 21.1.6 with SunOS 4.1.3's bundled X11 25 years, 3 months

Gunnar Evermann

Alexandre Oliva <oliva(a)dcc.unicamp.br> writes: > For src/ChangeLog > from Alexandre Oliva <oliva(a)dcc.unicamp.br> > > * tooltalk.c: Include signal.h, needed for struct sigaction on > SunOS 4.1.3. Oh, sorry, I hadn't checked when adding the sigaction stuff. but shouldn't we include "syssignal.h" instead? Gunnar

1 participants
0 comments

Re: Yeah! Using instructions missing from the README, xemacs ins talled! (was Re: How can xemacs have been made so hard to install? Do th e developers have any clue it is needlessly hard/undocumented?) 25 years, 3 months

Bless Terje

>I am leery of separating CVS components and we do not have a CVS >server running on www.xemacs.org. Maybe the thing to do is move the >webpages to cvs.xemacs.org and automatically mirror a checked out copy >to the webserver. Anyone interested in putting the scripts together >to do this? As in a cron job on www.xemacs.org that does "cd /html; cvs update"? :-) Or, if you dislike CVS client/server (can't that be tunneled over ssh, BTW?), you can keep a live site on cvs.xemacs.org and use one of the gazillion HTTP and/or FTP mirror utilities available.

1 participants
0 comments

Re: System type w/gcc2.95 on RH6 (was: ridiculously long subject) 25 years, 3 months

Bless Terje

>Terje Bless <link(a)rito.no> wrote: > ---------------------------------------------------------------------|----+- ---- >>...I just built GCC 2.95 on a Red Hat 6.0 box and removed the egcs rpms. >>This broke the config.guess (and thus breaks "configure") from XEmacs >>21.1.4. Somewhere in there it does a "ld --help" to extract the >>"supported emulations". For some strange reason, it only finds "elf_i386" >>and not "i386linux". I assume this is because ld's output format changed >>and the sed filter breaks, but I don't speak sed so I'm not sure. Forcing >>"i586-pc-linux" as an argument to "configure" works. > >Looking at the config.guess script it should _not_ find i386linux because >that is a.out. Something else must be wrong. [...] Surely we would have >know by now if every autoconf 2.13 based program stopped configuring >correctly with gcc 2.95 on redhat. So I suggest you double check your gcc >2.95 install: Ok, I finally had time to investigate this. Everyone is, of course, right and I bungled this. What happened was that when I removed the egcs 1.1.2 rpm from RedHat 6.0, I also removed the "cc" link that it installed. gcc 2.9.5 does not install such a link. Thus, "cc" was no longer in my path. "configure" and "config.guess" tries to call the compiler with "${CC-cc}" (which I thought meant "$CC or $cc" not "$CC or cc"; thus the confusion. Sorry about that!). Since $CC isn't set and "cc" isn't in my path, compiling the test program fails and "config.guess" exits silently with status "1". Now, this was without doubt my little brainfart, but OTOH it would be prudent of "configure" to check if a compiler is available before trying to use it. It obviously finds it later, as giving the config name works, but wouldn't be better to do that check before the first use of the compiler? Or at least complain when $CC and "cc" is not found and/or when "config.guess" returns an error? -link

1 participants
0 comments

Re: No gutter visible under AIX / X11 25 years, 3 months

Michael Sperber

>>>>> "MA" == ALTMARK <ALTMARK(a)de.ibm.com> writes: MA> Thanks for the advice! I think, for the moment I'll stay with the tarballs MA> as setting up efs to use cvs seems to be not that simple for our MA> site Actually, this won't work at all, and isn't meant to be. You pretty much have to use remote CVS. I can offer AFS access to a checked-out 21.2 which is updated reasonably frequently. (Usually at least every beta.) -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Yeah! Using instructions missing from the README, xemacs installed! (was Re: How can xemacs have been made so hard to install? Do the developers have any clue it is needlessly hard/undocumented?) 25 years, 3 months

Michael Sperber

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: sb> ... >> For me long-term fixes look like >> 1. Ditch the xemacs-announce list (or at least gate it to >> c.e.xemacs). sb> It should not be ditched. It is not subject to any of the whims and sb> badness that Usenet is subject to. It is possible to subscribe sb> xemacs(a)xemacs.org to it the same way xemacs-beta(a)xemacs.org is sb> subscribed to it. I've resisted doing this for various reasons, but sb> it is perhaps the best thing to do now. We should *definitely* route it to comp.emacs.xemacs, though. I just plain don't understand why people think that posting announcements to xemacs-announce is sufficient. We should announce everything we release---binary kits, minor releases---except for betas on comp.emacs.xemacs. We should also do comp.emacs and gnu.announce. This is extremely low-effort. We *need* more publicity, at least with especially after the long wait following 20.4 and the 21.0.67 announcement disaster. I'm also still all for formalizing stable and release branches the way FreeBSD does, and release stable every three or four months, whatever's on it. >> 2. Stick the website under CVS and have the www.xemacs.org server >> check it out every night. sb> I am leery of separating CVS components and we do not have a CVS sb> server running on www.xemacs.org. I don't understand why. Could you explain? sb> Maybe the thing to do is move the webpages to cvs.xemacs.org and sb> automatically mirror a checked out copy to the webserver. Anyone sb> interested in putting the scripts together to do this? I do know how to set up CVS such that it automatically checks out every commit right away. srfi.schemers.org is managed this way. If I can help, I'll volunteer. This simplifies updating the web site by an order of magnitude, and is likely to attract more volunteers as well. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Yeah! Using instructions missing from the README, xemacs installed! (was Re: How can xemacs have been made so hard to install? Do the developers have any clue it is needlessly hard/undocumented?) 25 years, 3 months

SL Baur

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: ... > For me long-term fixes look like > 1. Ditch the xemacs-announce list (or at least gate it to > c.e.xemacs). It should not be ditched. It is not subject to any of the whims and badness that Usenet is subject to. It is possible to subscribe xemacs(a)xemacs.org to it the same way xemacs-beta(a)xemacs.org is subscribed to it. I've resisted doing this for various reasons, but it is perhaps the best thing to do now. > 2. Stick the website under CVS and have the www.xemacs.org server > check it out every night. I am leery of separating CVS components and we do not have a CVS server running on www.xemacs.org. Maybe the thing to do is move the webpages to cvs.xemacs.org and automatically mirror a checked out copy to the webserver. Anyone interested in putting the scripts together to do this? > Jan > P.S. Yes the package system (or more precisely the way they are > released and distributed) has serious problems, but I think the above > problems are more fundamental. The package distribution problem is serious, but fixable and I'm working on it.

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 August 1999