June 1998 - XEmacs-Beta - XEmacs Mailing List Archives

column-number-mode bug 26 years, 5 months

Kyle Jones

Greg Klanderman writes: > If you have 2 windows showing the same buffer, both of their modelines > show the column number for the selected window. Line-number-mode > correctly shows a different value in each modeline. Patch follows. Patch looks OK. > [...] > So what ever happened with the column_number_start_at_one debate? My notes say, "Non-critical item. Tabled until 21.0 is released."

1 participants
0 comments

Popup menu bug 26 years, 5 months

Barry A. Warsaw

Seems like an old bug is back. Popup menus (e.g. right mouse over the [State] button in a Custom widget) are jammed against the right side of the screen instead of popping up underneath the pointer. -Barry -------------------- snip snip -------------------- uname -a: SunOS anthem 5.6 Generic_105181-04 sun4u sparc SUNW,Ultra-2 ./configure '--prefix=/depot/gnu' '--exec-prefix=/depot/gnu/plat' '--site-libraries=/depot/gnu/plat/lib /depot/sundry/plat/lib' '--site-includes=/depot/gnu/include /depot/sundry/include' '--infopath=/depot/gnu/info' '--error-checking=none' '--debug=no' '--with-mule=no' '--with-gcc=no' '--with-xpm=yes' '--with-database=gnudbm' '--with-cde=no' '--with-tooltalk=no' '--with-session=yes' '--with-offix=yes' XEmacs 21.0 "Toggenburg" configured for `sparc-sun-solaris2.6'. Where should the build process find the source code? /depot/gnu/src/xemacs-21.0-b46 What installation prefix should install use? /depot/gnu 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 -v -xO4 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/openwin/include Where do we find X Windows libraries? /usr/dt/lib /usr/openwin/lib Additional header files: /depot/gnu/include /depot/sundry/include Additional libraries: /depot/gnu/plat/lib /depot/sundry/plat/lib Runtime library search path: /depot/gnu/plat/lib:/depot/sundry/plat/lib:/usr/dt/lib:/usr/openwin/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 native sound support. Compiling in support for GNU DBM. Compiling in support for OffiX. Compiling in EXPERIMENTAL support for Drag'n'Drop ( 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 "dot-locking" for locking mail spool files.

1 participants
0 comments

Re: XEmacs 21.0 Package Building 26 years, 5 months

SL Baur

Oliver Graf <ograf(a)fga.de> writes: > What packages are considered core (i.e. should be inside a 'main' xemacs > distribution package), The minimal number to get an automatic package fetching system to work. That means right now it's basically `xemacs-base' and `efs'. A Mule build requires `mule-base'. > and which are considered auxilliary (i.e. the installers choice)? Everything else. > I'm currently writing a automatic package-get-base to rpm.spec converted > (including correct and easy to use dependencies). Cool! > I just wonder which package should go into the main tarball/rpm. Don't mix packages with the XEmacs core tarball. Packages can be updated after 'net release, the core cannot be until the next 'net release. > Or should none? At least the mule-stuff for a MULE enabled package... A case can be made for including `mule-base' since you cannot build XEmacs/Mule without it.

1 participants
0 comments

Re: package-get-base in XEmacs 21.0 "Toggenburg" 26 years, 5 months

SL Baur

Remek Trzaska <remek(a)npac.syr.edu> writes: > An entry for tm reads: > date "function, > " ... > It is harmless probably, but does not look nice for sure. Please use the new date format on all ChangeLog entries. It is used to generate the tag used for the `date' field. If someone wishes to fix this to work with old-style ChangeLog entries, the code is in package-info.el (pi-last-mod-date). Index: ChangeLog =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-packages/comm/tm/ChangeLog,v retrieving revision 1.8 diff -u -r1.8 ChangeLog --- ChangeLog 1998/06/15 05:54:27 1.8 +++ ChangeLog 1998/06/24 05:03:05 ＠＠ -1,4 +1,4 ＠＠ -Tue Jun 09 23:04:08 1998 Darryl Okahata <darrylo(a)sr.hp.com> +1998-06-09 Darryl Okahata <darrylo(a)sr.hp.com> * (TM 1.07: tm-edit.el) Added new function, `mime-editor/insert-file-verbose', so that users can use menu

1 participants
0 comments

Re: XEmacs 21.0b46, Packages 26 years, 5 months

SL Baur

Barry A Warsaw <bwarsaw(a)CNRI.Reston.Va.US> writes: > I know next to nothing about how the new package stuff works, but even > so, it was pretty painless for me get the packages I wanted installed > and working with XEmacs 21. It worked very well in my strange > /depot/gnu installation :-) Kudos to all! Cool! ... > 2. Now that I've got all the packages installed, what tools are > available for me to uninstall packages (see below), get updates > from the net (perhaps with signature verification), etc. Formal uninstallation support is lacking at present. It hasn't been forgotten and there will be some support by release time. One of the Golden Rules of packages is that `leaf' regular packages (like Supercite) may have all their installed files deleted without harm. Individual .el files in single-file packages may be deleted without harm (like lazy-lock.el in the edit-utils package). > 3. I had a problem with the skk package. It seems I downloaded and > installed that but built XEmacs w/o MULE There's a naming convention to allow Mule packages to coexist with non-Mule XEmacs builds. Put your non-Mule packages in `xemacs-packages' and your Mule packages in `mule-packages'. Any packages in a `mule-packages' hierarchy are left untouched in a non-Mule XEmacs.

1 participants
0 comments

XEmacs 21.0b46, Packages 26 years, 5 months

Barry A. Warsaw

I just downloaded and installed 21.0b46. Note that I haven't really been following things lately, and in fact have been off this list since my son was born (just don't have the time). I know next to nothing about how the new package stuff works, but even so, it was pretty painless for me get the packages I wanted installed and working with XEmacs 21. It worked very well in my strange /depot/gnu installation :-) Kudos to all! Of course, you probably wouldn't hear from me if I didn't have at least a few nits and questions: 1. Will there be a godzilla-package that contains everything I'd need to destroy Reston... er, I mean fill up my disk. I've got a good network connection and lots of disk space to burn, so I just want to install everything. How easy will it be for me to do this, when XEmacs 21 is released? I had to pull down each individual package, which was time consuming trying to figure out what was what. 2. Now that I've got all the packages installed, what tools are available for me to uninstall packages (see below), get updates from the net (perhaps with signature verification), etc. The XEmacs info manual doesn't seem to talk much about package tools, and I don't know of a good way to find out what packages have been updated since I last downloaded them circa b44. (yes I know I could read Steve's announcements, but still, that's not a good general solution). 3. I had a problem with the skk package. It seems I downloaded and installed that but built XEmacs w/o MULE (since none of my people use it anyway). XEmacs would not start since the skk package got loaded at run-time (somehow), but it couldn't load `mule'. Seems like skk should be a little more robust. I eventually just rm'd packages/lisp/skk/, packages/etc/skk/, and packages/info/skk* but I didn't know if there were better tools to do package management. Anyway, good work to all. I go to play. One thing I did notice is that the modeline colors are different now. Oh well, that's what Custom is for eh? Please CC me on any followups. Thanks, -Barry

1 participants
0 comments

[SUCCESS] 21.0 "Toggenburg" XEmacs Lucid on i386-unknown-freebsd2.2.6 26 years, 5 months

C Matthew Curtin

> XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /home/cmcurtin/xemacs-21.0-b46/Installation: > (Output from most recent run of ./configure) uname -a: FreeBSD scooter.cis.ohio-state.edu 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: Wed Mar 25 02:28:49 GMT 1998 jkh＠time.cdrom.com:/usr/src/sys/compile/GENERIC i386 ./configure '--prefix=/usr/local/xemacs-21' XEmacs 21.0 "Toggenburg" configured for `i386-unknown-freebsd2.2.6'. Where should the build process find the source code? /home/cmcurtin/xemacs-21.0-b46 What installation prefix should install use? /usr/local/xemacs-21 What operating system and machine description files should XEmacs use? `s/freebsd.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 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 Runtime library search path: /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for OffiX. Compiling in EXPERIMENTAL support for Drag'n'Drop ( 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 "flock" for locking mail spool files. > /home/cmcurtin/xemacs-21.0-b46/beta.err does not exist! -- Matt Curtin Just Another (Perl|Java|Unix|.*) Hacker http://www.cis.ohio-state.edu/~cmcurtin/ mailto:cmcurtin＠cis.ohio-state.edu

1 participants
0 comments

Re: Lisp shadowings 21.0 "Toggenburg" XEmacs 26 years, 5 months

SL Baur

Paul Bibilo <peb(a)delcam.com> writes: > I CVS updated everything. Built OK. When you install, rm -rf the previous installed lisp directory, eg. when installing xemacs-base, `rm -rf lisp/xemacs-base' first. Most of these shadows will go away once the packages are properly installed. > /devdisk/d54man/gnu/xemacs-beta/packages/lisp/dired/dired hides /devdisk/d54man/gnu/xemacs-beta/packages/lisp/efs/dired Dired was split out of EFS. The current EFS package does not have them. > /devdisk/d54man/gnu/xemacs-beta/packages/lisp/edit-utils/timer hides /devdisk/d54man/gnu/xemacs-beta/packages/lisp/fsf-compat/timer > /devdisk/d54man/gnu/xemacs-beta/packages/lisp/fsf-compat/overlay hides /devdisk/d54man/gnu/xemacs-beta/packages/lisp/xemacs-base/overlay timer.el and overlay.el are no longer part of the xemacs-base package and you will not find them in the current version. > /devdisk/d54man/gnu/xemacs-beta/packages/lisp/edit-utils/tempo hides /devdisk/d54man/gnu/xemacs-beta/packages/lisp/psgml/tempo tempo.el was moved to edit-utils and is no longer a part of psgml (nor does it appear in the current version). > /devdisk/d54man/gnu/xemacs-beta/packages/lisp/reftex/reftex hides /devdisk/d54man/gnu/xemacs-beta/packages/lisp/textools/reftex reftex was moved into its own package and removed from textools. > /devdisk/d54man/gnu/xemacs-beta/packages/lisp/vc/vc hides /devdisk/d54man/gnu/xemacs-beta/packages/lisp/vc-cc/vc > /devdisk/d54man/gnu/xemacs-beta/packages/lisp/vc/vc-hooks hides /devdisk/d54man/gnu/xemacs-beta/packages/lisp/vc-cc/vc-hooks These are true shadows. Don't install both vc and vc-cc. This is supposed to be documented somewhere. The vc-cc package was provided for the convenience of the developers attempting to update the ClearCase support that was removed when a previous version of vc was synched with FSF Emacs. > I've reported these lisp shadowings before, I know. > and as I synch via CVS, I assume that it's a problem in the package > hierarchy. These have been present for a good few betas now. It's only a problem with your installation.

1 participants
0 comments

21.0 "Toggenburg" : problem with info files 26 years, 5 months

Richard Cognot

While browsing the info files generated by makeinfo 1.68 for xemacs, I noticed that quite a few nodes were not reachable. Turns out my info files sometimes contain a leading char before the seperation character. Removing these from the info files fixes the problem. Don't know whether it's a makeinfo bug, or if XEmacs should account for that, though... info.el searches for \n\^_ in a lot of places, so any leading space is going to cause problems. Richard. -- |-------------------------------------------------------------| | Richard Cognot | Proceed, with fingers crossed... | | | /\^^/\ | | <cognot(a)ensg.u-nancy.fr> | `' | |-------------------------------------------------------------| | http://www.ensg.u-nancy.fr/~cognot | |-------------------------------------------------------------|

1 participants
0 comments

Re: More C mode syntactic yuckage 26 years, 5 months

Hrvoje Niksic

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Without saved state, it is impossible to tell whether you're inside > or outside a comment without starting from the beginning of the > buffer, sweeping through the buffer and watching what comment and > string delimiters go by. On a different note: how about that "without saved state"? Don't we have syntactic cache in font-lock.c? Could that cache be used elsewhere in XEmacs? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Call CIA and tell them that you have placed a bomb in a 7-11 shop! Be sure to let them trace you. Spend 10 years in jail and then regret 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 June 1998