May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Hrvoje Niksic

Try this: split window with `C-x 3', and place scrollbar on the left like this: (set-specifier scrollbar-on-left-p t (selected-window)) Now the left window has a scrollbar on the left, and the right window has a scrollbar on the right. Between them should be a separator -- but there is none! -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- We are all just prisoners here of our own MAKEDEV.

1 participants
0 comments

[Success] "Russian White" XEmacs 27 years

Rebecca Ore

I'm having some weird problems with, I think, kde renaming my machine, but here it is after rebuilding on the console, and here is the installation file. When will the new mailing list be ready? uname -a: Linux d-phlarc3-02 2.0.30 #6 Sat Apr 25 16:18:07 EDT 1998 i586 ./configure '--cflags=-g -m486 -Wall -O3 -fno-caller-saves -fno-strength-reduce -malign-loops=2 -malign-jumps=2 -malign-functions=2' '--with-xface=yes' '--error-checking=none' '--debug=no' '--with-png=yes' '--with-jpeg=yes' '--with-mule=yes' '--with-site-lisp=yes' XEmacs 21.0-b39 "Russian White" configured for `i586-pc-linux'. Where should the build process find the source code? /home/rebecca/xemacs-21.0-b39 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 -m486 -Wall -O3 -fno-caller-saves -fno-strength-reduce -malign-loops=2 -malign-jumps=2 -malign-functions=2 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 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 native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM 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. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files.

1 participants
0 comments

[Success] 21.0 "Russian White" XEmacs Lucid (beta39) on i686-pc-linux 27 years

Hayashi Tanaka

Patched up from beta38. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /home/tanaka/src/xemacs-21.0-b39/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

[Success] XEmacs 21.0-b39 on Linux 27 years

Kazuyoshi Furutaka

[i686-GNU-linux] Source : patched up from 21.0 beta38 Patch : patch 2.4 Make : GNU Make version 3.76.1 CC : pgcc-2.90.27 980315 (egcs-1.0.2 release) OS : Linux 2.0.34pre11b (RedHat 5.0) X : X11R6.3 (Accelerated-X ver.4.1 w/ XFree86 3.3.1) gdb : GDB 4.16 [alpha-GNU-linux] Source : patched up from 21.0 beta38 Patch : Patch version 2.1 Make : GNU Make version 3.75 CC : egcs-2.90.23 980102 (egcs-1.0.1 release) OS : Linux 2.1.89 (StataboWare) X : X11R6.3 (XFree86 3.3.2) gdb : GDB 4.16 -- Kazuyoshi Furutaka furutaka(a)tokai.pnc.go.jp furutaka(a)jb3.so-net.ne.jp

1 participants
0 comments

Packages in NEWS 27 years

Hrvoje Niksic

Currently, the entry for packages in NEWS looks like this: ** XEmacs has been unbundled into constituent installable packages. See the file `etc/PACKAGES' in the distribution for a full description. I am not satisfied with this. etc/PACKAGES is too large and contains lots of unnecessary information. I feel someone acquainted with the package system (Michael? Steve?) should write a few entries intended for XEmacs users to read, with the additional pointer to etc/PACKAGES for more info. Do you agree with this? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- ED WILL NOT CORRUPT YOUR PRECIOUS BODILY FLUIDS!!

1 participants
0 comments

New list address -- xemacs-build-reports@xemacs.org 27 years

SL Baur

In a continuing effort to sort information that may not be of general use on xemacs-beta, we have set up a destination for XEmacs beta build reports --- xemacs-build-reports(a)xemacs.org. This is a majordomo mailing list should anyone wish to subscribe. It is not required to be subscribed to email to it. The list information follows ... xemacs-build-reports is an open list for submission of build-reports on beta versions of XEmacs. For information on what the build-reports should contain, please see the `etc/BETA' file which is included in each beta distribution. To subscribe to xemacs-build-reports, send an email message to xemacs-build-reports-request(a)xemacs.org with `subscribe' (without the quotes) as the BODY of the message.

1 participants
0 comments

XEmacs 21.0-beta39 "Russian White" is released 27 years

SL Baur

The next edition of XEmacs 21.0 has been uploaded to the ftp site. ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.0/ CVS sources are at http://cvs.xemacs.org/ Installable Lisp packages are in: ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.0/packages/binary-packages/ The CVS tag for this beta is `r21-0b39'. To read about the Russian White Goat please see: http://www.ansi.okstate.edu/breeds/goats/russian/index.htm * Comments First some really good news. :-) The fine folks at the Oklahoma State University Agriculture department added 11 new goat breed names to their web page, so we're not nearly as short on beta-21.0 names as I had originally thought. I'm sure this comes as a relief to everyone. :-) We've decided to push forward on Drag'n'Drop and try to get _something_ into the 21.0 release. Hopefully it will be something better than just wildly experimental. Please see the tests in tests/Dnd (droptest.el and dragtest.el) and give them a spin and see well they work or don't work. *IMPORTANT* Due to the name change of the file formerly known as x-menubar.el, you will need to upgrade your mule-base package if you are using XEmacs/Mule, otherwise you won't have the Mule menu items `Describe Language Support' and `Set Language Environment'. *IMPORTANT* If you are using LDAP support, you will also need to update your eudc package. As usual there are lots of bug fixes. Note that etags has been reverted to the version used in XEmacs 20.4. An experimental enhanced version of etags has been added as ootags. We're in feature slush. Full feature freeze is now formally scheduled for May 15th, midnight UT (5PM US/Pacific). I'd like to plan on about two weeks of cooling off where a lot of time is spent enumerating and chasing down visible problems, and have a full code freeze (show stopping bug fixes only) for at least two weeks prior to 'net release. With usual slippage, perhaps we can have a release after the 4th of July. * Updated packages The following packages have been updated on the FTP site: mail-lib-1.13 Redefine as regular package, customize `message-url' face. eudc-1.06 EUDC-1.06 (Required for this beta if you are using LDAP) dired-1.01 Use easymenu supercite-1.06 Autoload sc-cite-original, defcustom fix pcl-cvs-1.08 backup file not found fix * Recent Changes There's a lot of new MS Windows support in this, including toolbar, processes, and Xpm. I'm happy with the package path/startup path stuff for the first time in a number of betas. Hopefully, we're past the worst of the changes. All path stuffs should work again. The configure option --gung-ho now controls whether minimal tagbits and indexed lrecords are used. Please test the -elc tarball with this beta. I've generated it from a tty-only build for testing. While this should work (and the build now currently assumes it does work), and it seems to work for me, it needs as much testing as possible prior to release. Canna detection should work better. LDAP support should build and run. Multicast support should build and run. The default target of `make' is to build everything. This is almost what `make dist' used to do except that finder-inf.el (the finder database) gets properly bytecompiled. DLL support is now autodetected. The configure option `--with-dlmalloc' has been added so that gmalloc.c can still be used on systems with the Doug Lea new GNU Malloc. The Installation file format has changed slightly -- the version number is now printed in the summary, old copies are not retained, so if you wish old copies you will have to make the copy by hand. The Installation summary is available via the command M-x describe-installation. `XEmacs' can be used for X resources. This feature needs further testing but appears to work. dlmalloc now works with mmap'ping enabled for Linux Libc5 systems. I'm very interested in reports on how XEmacs' virtual memory footprint changes with time with dlmalloc. My own experiences with mmap disabled (only for glibc-2.0 and Mule) show a net win over 20.4. I'm hoping mmap improves things further. The source-packages subdirectory on the FTP site has been abolished in favor of distributing Lisp sources via CVS. The minimum required packages are the following: [Only xemacs-base updated since the last beta, the package version number is relatively unimportant] xemacs-base-1.19-pkg.tar This package contains core functionality not dumped into XEmacs. It includes things like the debugger, comint, overlay, ring, etc. mail-lib-1.13-pkg.tar This package contains core functionality common to mail and newsreading. If you are building on a Sun with tooltalk and/or Sparcworks you will also need the Sun and tooltalk packages. These packages should be installed prior to dumping XEmacs. *NOTE* you will need to patch one of the system lisp files to do proper v21 detection if you have not already done so. *NOTE:* As of beta39, you must use mule-base-1.16 or later. Note also, as of beta34, overlay.el has been moved to the fsf-compat package. If you are building with Mule, you will need to have the mule-base package installed *prior* to dumping XEmacs or you will lose. If you see messages about mule-charset not found, or get a bomb immediately after seeing a message about `loading ... dialog', then you need to stop and install the mule-base package. Other various packages need to be installed prior to dumping XEmacs. They are marked with `dump t' in the package description, see package-get-base.el and package-get.el for an interface. ** ImageMagick has gone away courtesy of Jareth Hein. ** The generalization of the XEmacs internals has continued. Quoting Kyle Jones: If you're feeling maximally gung, add -DUSE_MINIMAL_TAGBITS and -DUSE_INDEXED_LRECORD_IMPLEMENTATION to your compiler flags when you build 20.5. If all is well XEmacs should build and run normally. Update: These options are now enabled by specifying `--gung-ho'. -DUSE_MINIMAL_TAGBITS will be automatically set if using dlmalloc. NOTE: It should *never* be required to use these options for proper operation of XEmacs (with the single exception of -DUSE_MINIMAL_TAGBITS for dlmalloc). A failure _without_ these options set is a bug that needs to be fixed. ** Chinese and Korean Wnn server support has been added to LEIM. Someone familiar to cWnn and kWnn will need to test this out. I haven't heard any reports positive or negative yet. * Futures ** 21.0-beta40 is scheduled for Saturday, May 16. ** The highest priority is getting things ready for code freeze. ** Depending upon the level of patching activity, there will be several interim pre-betas for further testing. For those not acquainted with recent XEmacsen (things have changed since 20.3/21.0-b11), there are 4 files in the distribution. Each file has been PGP signed. *** xemacs-21.0-b38-21.0-b39.patch.gz This is a patch from the previous release. Please see the file etc/BETA for patching instructions. As of beta13 we're through the worst of the reorganizations and patching should be pretty smooth from here on out. *** xemacs-21.0-b39.tar.gz This is the core distribution without bytecompiled lisp and without processed texinfo manuals. If you are on a fast machine with a possibly slow connection to the FTP site, this is all you need for an XEmacs non-mule. Untar it, run configure, then run `make' and `make install'. *** xemacs-21.0-b39-info.tar.gz This the processed texinfo manuals. If you have makeinfo installed and your machine has any kind of decent speed, it is quicker to run `make info' from the toplevel and rebuild it yourself than it is to download and untar it. You will need a fairly recent version of makeinfo in order to be able process all the info documentation. At least `makeinfo (GNU texinfo 3.11) 1.68' is recommended. Note that the latest version of GNU texinfo is now 3.12. *** xemacs-21.0-b39-elc.tar.gz This is the bytecompiled lisp. It was freshly bytecompiled from scratch prior to distribution. to 21.0 beta39 "Russian White" -- DnD fixes from Oliver Graf and Jonathan Harris -- scrollbar visibility and placement specifiers from of Kirill Katsnelson -- x-toolbar.el and x-menubar.el renamed to toolbar-items.el and menubar-items.el -- Device metrics from Kirill Katsnelson -- Frame redraw smoothing fix from Kirill Katsnelson -- MS Windows transparency handling from Andy Piper -- XEmacs FAQ update from Christian Nybo -- MS Windows build fix for minimal tagbits, etc. from Kirill Katsnelson -- Fix cancelling directory creation prompt from Hrvoje Niksic -- cygwin build fixes from Andy Piper -- Restore oo-browser etags.c as ootags.c -- Socket connections for Windows from Kirill Katsnelson -- region limiting fixes from Hrvoje Niksic -- cleanup focus-follows-mouse handling from Greg Klanderman -- mswindows cursor support from Andy Piper -- elimination of bzero from Michael Sperber -- build fix from Jeff Miller -- xpm button fix from Andy Piper -- add optional `norecord' arg to select-window from Greg Klanderman -- regexp quote fix from Hrvoje Niksic -- early frame title update from Jan Vroonhof -- Make character 0240 display as space from Kyle Jones -- 0 argument printing fix from Hrvoje Niksic -- revert recent changes to etags.c -- dump clean up, removal of Lisp reader macros -- spelling fix from Jonathan Harris -- MS Windows build fix from Kirill Katsnelson -- sound fixes from Kyle Jones -- LDAP updates from Oscar Figueiredo -- Drag and drop update from Oliver Graf -- rename XEmacs internal realpath from Kyle Jones -- rangetab cleanup from Martin Buchholz -- etags fix -- miscellaneous bug fixes

1 participants
0 comments

Re: [Q] Should `string' accept integers? 27 years

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > > No. Even if we accept integers, this is a kludge liable to change, > > and should be (un)documented as such. No correct code should ever > > rely on `string' accepting integers. > > I mean it should have the kind of warning `concat' has. Oh. Well, concat has that warning because it existed long before XEmacs/Mule. I don't see the gain by actually *introducing* broken behavior to a new function and then adding a warning not to use it. > [...] Oh, the comment in `concat' is wrong: > > (concat 65 65) > => "6565" This is the hysterical behaviour, yes. What comment are you referring to? > Well, make `string' consistent. > > (string 65) > => "65" Yuck. I don't think we want to do anything like this. FSFmacs doesn't do it. (string 65) => "A" -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- A radioactive cat has eighteen half-lives.

1 participants
0 comments

Re: [Q] Should `string' accept integers? 27 years

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes: > SL Baur <steve(a)xemacs.org> writes: >> > Another question: do we care about FSF compatibility? FSF also has >> > `string', and they certainly accept integers. >> >> We care where it otherwise hurts. If it's going to accept integers >> the DOC string needs to be corrected. > No. Even if we accept integers, this is a kludge liable to change, > and should be (un)documented as such. No correct code should ever > rely on `string' accepting integers. I mean it should have the kind of warning `concat' has. [...] Oh, the comment in `concat' is wrong: (concat 65 65) => "6565" Well, make `string' consistent. (string 65) => "65"

1 participants
0 comments

Re: [Q] Should `string' accept integers? 27 years

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > > Another question: do we care about FSF compatibility? FSF also has > > `string', and they certainly accept integers. > > We care where it otherwise hurts. If it's going to accept integers > the DOC string needs to be corrected. No. Even if we accept integers, this is a kludge liable to change, and should be (un)documented as such. No correct code should ever rely on `string' accepting integers. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Sauron is alive in Argentina!

1 participants
0 comments

2025

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