XEmacs-Beta March 1999

xemacs-beta@xemacs.org

121 participants
488 discussions

Re: XEmacs 21.0.64 "20 minutes to 日光" is released 25 years, 2 months

Gunnar Evermann

what's the current status of your patch queues? I'm missing: [21.0 and 21.2] document gcc/SPARC bug http://www.xemacs.org/list-archives/xemacs-patches/9901/msg00013.html Have I missed someone vetoing that? we really need to address this problem somehow. I can't stand any more of these boring backtraces in the BugTracking System. :-) Gunnar

1 participants
0 comments

[buildreport] 21.2b11 25 years, 2 months

Neal D. Becker

(1) (warning/warning) Autoload error in: /usr/local/lib/xemacs/xemacs-packages/lisp/c-support/auto-autoloads: Symbol's value as variable is void: hide-ifdef-mode-map uname -a: Linux nbeckerpc.hns.com 2.2.1 #7 Mon Feb 1 14:00:59 EST 1999 i686 unknown ../../xemacs-21/configure '--gung-ho' XEmacs 21.2-b11 "Calliope" configured for `i686-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21 What installation prefix should install use? /usr/local 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 -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) 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 PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. 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 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 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

Distribution Build Report for XEmacs-21.0.64 25 years, 2 months

Steven Baur

Greetings XEmacs beta testers. I am in the process of building the next distribution of XEmacs 21.0. I have tested the attached configuration. Sincerely, The XEmacs Build 'Bot -- uname -a: BSD/OS camelot-soft.camelot-soft.com 3.0 BSDI BSD/OS 3.0 Kernel #0: Thu Jul 17 23:30:01 PDT 1997 root＠camelot-soft.camelot-soft.com:/usr/src/sys/compile/CAMELOT i386 ./configure '--prefix=/usr/home/steveb/staging' '--cflags=-O' '--with-mule' '--without-x11' '--debug=no' '--error-checking=none' XEmacs 21.0-b64 "20" configured for `i386-pc-bsdi3.0'. Where should the build process find the source code? /usr/home/steveb/staging/xemacs-21.0 What installation prefix should install use? /usr/home/steveb/staging What operating system and machine description files should XEmacs use? `s/bsdos3.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -O Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? none Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in Mule (multi-lingual) support. Compiling in DLL support. movemail will use "flock" for locking mail spool files.

2 participants
1 comments

XEmacs 21.2.11 "Calliope" is released 25 years, 2 months

SL Baur

Get it from the usual places: ftp://ftp.xemacs.org/pub/xemacs/beta/ http://cvs.xemacs.org/ There has been a minor amount of reorganization to make the build cleaner. Having the mule-base package around is no longer required for building XEmacs mule so the XEmacs core is self-contained again. Please update mule-base to 1.28 ftp://ftp.xemacs.org/pub/xemacs/packages/mule-base-1.28.tar.gz to avoid unnecessary lisp shadows. 21.2.12 is scheduled for Friday, but if anything slips in the schedule, it's first on the list to be postponed. to 21.2 beta11 "Calliope" -- Dialog box fix from Jan Vroonhof -- unified mswindows and tty event loops from Andy Piper -- miscellaneous patches from Gleb Arshinov -- miscellaneous patches from Charles Waldman and Adrian Aichner -- Mule dump time files remerged from mule-base package -- Documentation fixes from Jan Vroonhof -- 24bit color image fix from Kazuo OISHI -- various build fixes from Martin Buchholz

1 participants
0 comments

XEmacs 21.0.64 "20 minutes to 日光" is released 25 years, 2 months

SL Baur

Get it from the usual places: ftp://ftp.xemacs.org/pub/xemacs/beta/ http://cvs.xemacs.org/ There has been a minor amount of reorganization to make the build cleaner. Naturally, something went wrong. In order to get the name right, please apply the following patch if you are not using CVS to update with. If this is the only new thing wrong[1], I'll be happy ... Index: version.sh =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/version.sh,v retrieving revision 1.144 retrieving revision 1.145 diff -u -r1.144 -r1.145 --- version.sh 1999/03/01 18:11:26 1.144 +++ version.sh 1999/03/01 19:26:49 1.145 ＠＠ -2,7 +2,7 ＠＠ emacs_major_version=21 emacs_minor_version=0 emacs_beta_version=64 -xemacs_codename="20" +xemacs_codename="20 minutes to Nikko" infodock_major_version=4 infodock_minor_version=0 infodock_build_version=6 Building with Mule should be a little easier now. Mulish dumped lisp files are now distributed with the core. I will separate them out into a separate tarball if there are any problems with Latin-1 XEmacs, but I didn't find any in my own testing. You will need the latest & greatest mule-base package in order to avoid lots of Lisp shadows. ftp://ftp.xemacs.org/pub/xemacs/packages/mule-base-1.28.tar.gz Install that prior to building the new version and make sure that the previous directory, lisp/mule-base, gets `rm -rf'ed prior to installation of the update. There will be a new 21.0 release in very short order, definitely by the end of the week. I'm aiming for Friday. to 21.0 "20 minutes to Nikko" -- Dialog box fix from Jan Vroonhof -- prevent minimization of maximized frame from Andy Piper -- miscellaneous patches from Andy Piper and Gleb Arshinov -- miscellaneous patches from Charles Waldman and Adrian Aichner -- Mule dump time files remerged from mule-base package -- Documentation fixes from Jan Vroonhof -- 24bit color image fix from Kazuo OISHI -- various build fixes from Martin Buchholz Footnotes: [1] I already know about the hideifdef breakage, but I won't have time to fix it tonight. An update will be coming first thing in the morning.

1 participants
0 comments

New XEmacs SUMO lisp tarballs are available 25 years, 2 months

SL Baur

If you are running with Mule, you will need the mule-sumo. If you are not running with Mule, you don't. Updated packages include: text-mode-1.18 Install htmlize.el gnus-1.38 Don't install pop3.el mule-base-1.28 [1] All dumped lisp files removed as they will be distributed again with the XEmacs core. c-support-1.11 hideifdef keymap fix w3-1.12 Update to W3-4.0-pre39 vm-1.16 Update to VM-6.67 calendar-1.10 Autoload holiday apel-1.09 New support for file-coding compile-time option xemacs-base-1.30 imenu fix for Python vc-1.17 ??? viper-1.13 ediff-1.17 eudc-1.28 Various updates edit-utils-1.37 New version of after-save-commands.el prog-modes-1.18 f90.el update Footnotes: [1] Incompatible with prior mule-base packages. Be sure that the lisp/mule-base directory is rm -rf'ed prior to installation if you're installing by hand. You will also need XEmacs 21.0.64 and/or 21.2.11 in order to build XEmacs/Mule. Prior versions of mule-base will be O.K. with 21.0.64+ and 21.2.11+, but you will have to ignore all the Lisp shadows.

1 participants
0 comments

Re: caller GCPROs? 25 years, 2 months

Gunnar Evermann

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: > > > Is there any particular reason for this rather obvious lie ('This > > function can GC') at insdel.c:2644? > > > > --------------- > > Charcount > > buffer_insert_from_buffer_1 (struct buffer *buf, Bufpos pos, > > struct buffer *buf2, Bufpos pos2, > > Charcount length, int flags) > > { > > /* This function can GC */ > > Lisp_Object str = make_string_from_buffer (buf2, pos2, length); > > return buffer_insert_string_1 (buf, pos, 0, str, 0, > > XSTRING_LENGTH (str), flags); > > } > > That's no lie. buffer_insert_string_1() can not only GC, but invoke > arbitrary Lisp code! Remember {before,after}-change-functions. I know. Maybe I misunderstood all those 'can GC'-comments. I assumed them to mean: - during execution of this functions Lisp code might be called and potentially GC can occur - this code is GC-safe, meaning it GCPROs all local Lisp_Objects and therefore a GC won't collect vital stuff. My question was basically why we don't GCPRO 'str' and then use RETURN_GCPRO, to ensure the second point. Sorry for the confusion. Gunnar -- Gunnar Evermann Speech, Vision & Robotics Group Engineering Department Cambridge University

1 participants
0 comments

[NT4SP3] movemail buggy 25 years, 2 months

Sebastien Carpe

with movemail. my aim is to have some MTA to download messages from pop3 to file, then have procmail to parse the file and use the result as a spool file for VM (and another spool file to send mailing lists to Gnus). The MTA i found and procmail seems to work fine, yet, i've a loss of mail when they are transfered from spool file to my primary inbox. Actually, only 1000 bytes were copied when i first tried, and when i try to use movemail from command-line (movemail -i <spool file> -o <inbox>), only 1024 bytes are transfered. This is really odd... Since i've seen any mentyion of this anywhere, i suspect to have some kind of misconfiguration somewhere... Since the 1k bytes seems to be a pretty meaning limits, i'll cross-post this to xemacs-beta, just in case it does mean anything to someone friendly with that piece of code. Thanx for any clue about this, Seb C.

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