April 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: AUCTeX byte-compile problems in tex-jp.el 25 years, 12 months

Jim Radford

SL Baur <steve(a)xemacs.org> writes: Oops, the problem is that tex-jp.el wont compile without mule (it even says this at the top of the Makefile if I would have looked). In case anyone else runs into this, you have to make the xemacs-packages with make bindist MULE_ELCS= if you haven't compiled with mule, otherwise the build of AUCTeX (and I assume, other packages that I don't use) will fail. > Jim Radford <radford(a)robby.caltech.edu> writes: > > > I have no idea what these strings are supposed to be/say, but I know > > they don't compile. I'm surprised I haven't seen this mentioned. > > I guess no one uses AUCTeX. > > > === cd /home/radford/xemacs/xemacs-packages/wp/auctex/ > > === cvs -d :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot diff -u tex-jp.el > > tex-jp.el can only be used and bytecompiled with XEmacs/Mule -- it worked > fine there the last time I tested it. AUCTeX works fine, lots of > people use it.

1 participants
0 comments

[Success] 21.0 "Repartida-pre1" XEmacs Lucid (beta38) on i586-pc-linux 25 years, 12 months

John Mignault

Patched from b37, and then applied Jareth's image corruption patch afterwards. No problems so far. J > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/src/xemacs-20.5-b33/Installation: > (Output from most recent run of ./configure) uname -a: Linux jbm 2.0.31 #1 Sun Nov 9 21:45:23 EST 1997 i586 unknown ./configure '--dynamic' '--with-database=gnudbm' '--with-xpm' '--gung-ho' XEmacs 21.0-b38 "Repartida-pre1" configured for `i586-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-20.5-b33 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 -O2 -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 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 GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for 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. 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: --------------------------------------------------------- > /usr/local/src/xemacs-20.5-b33/beta.err does not exist!

1 participants
0 comments

Re: [PATCH] xmine patch 25 years, 12 months

Hrvoje Niksic

Andy Piper <andyp(a)parallax.co.uk> writes: > xmine now looks fab under mswindows:) Heh, it should be renamed to `winmine' now that it works on other window systems. But that name would be kind of ambigous, too. :-) Also, Jens should replace `window-system' with `(console-on-window-system-p)'. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- If anything goes wrong, blame the random-number generator!

1 participants
0 comments

Re: [BUG] in minibuffer history ? 25 years, 12 months

Hrvoje Niksic

Didier Verna <verna(a)inf.enst.fr> writes: > --- lisp/minibuf.el.org Wed Apr 29 18:23:11 1998 > +++ lisp/minibuf.el Wed Apr 29 18:23:17 1998 > ＠＠ -319,7 +319,7 ＠＠ > (defvar current-minibuffer-contents) > (defvar current-minibuffer-point) > > -(defcustom minibuffer-history-minimum-string-length 3 > +(defcustom minibuffer-history-minimum-string-length nil > "*If this variable is non-nil, a string will not be added to the > minibuffer history if its length is less than that value." > :type '(choice (const :tag "Any" nil) > You forgot the changelog entry: 1998-04-29 Didier Verna <verna(a)inf.enst.fr> * minibuf.el (minibuffer-history-minimum-string-length): Default to nil. It is very important that changes like this are documented in the changelog, so that if something breaks we can investigate what caused the breakage. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- ED WILL NOT CORRUPT YOUR PRECIOUS BODILY FLUIDS!!

1 participants
0 comments

Re: [BUG] in minibuffer history ? 25 years, 12 months

Didier Verna

Hrvoje Niksic <hniksic(a)srce.hr> writes: > greg(a)alphatech.com (Greg Klanderman) writes: > > > see: > > > > (defcustom minibuffer-history-minimum-string-length 3 > > "*If this variable is non-nil, a string will not be added to the > > minibuffer history if its length is less than that value." > > :type '(choice (const :tag "Any" nil) > > integer) > > :group 'minibuffer) > > Could we please default this to nil? The default is horrible and > violates the principle of least surprise. Such a "feature" does not > exist in GNU Emacs. Agreed 100%. I was *most* surprised ;-) --- lisp/minibuf.el.org Wed Apr 29 18:23:11 1998 +++ lisp/minibuf.el Wed Apr 29 18:23:17 1998 ＠＠ -319,7 +319,7 ＠＠ (defvar current-minibuffer-contents) (defvar current-minibuffer-point) -(defcustom minibuffer-history-minimum-string-length 3 +(defcustom minibuffer-history-minimum-string-length nil "*If this variable is non-nil, a string will not be added to the minibuffer history if its length is less than that value." :type '(choice (const :tag "Any" nil)

1 participants
0 comments

Re: [BUG] in minibuffer history ? 25 years, 12 months

Hrvoje Niksic

greg(a)alphatech.com (Greg Klanderman) writes: > see: > > (defcustom minibuffer-history-minimum-string-length 3 > "*If this variable is non-nil, a string will not be added to the > minibuffer history if its length is less than that value." > :type '(choice (const :tag "Any" nil) > integer) > :group 'minibuffer) Could we please default this to nil? The default is horrible and violates the principle of least surprise. Such a "feature" does not exist in GNU Emacs. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Union break!

1 participants
0 comments

[PATCH] xmine patch 25 years, 12 months

Andy Piper

xmine now looks fab under mswindows:) andy 1998-04-29 Andy Piper <andyp(a)parallax.co.uk> * xmine.el: predicate on window-system not 'x.

1 participants
0 comments

[PATCH] background pixmaps in mswindows 25 years, 12 months

Andy Piper

[I'm at home 'cause my wife is ill - so I get to hack a lot :)] This was bizarrely easy to do. So now customize looks nice. xmine still looks bad because it predicates everything on 'x rather than just 'xpm, maybe Jens could fix this ? andy 1998-04-29 Andy Piper <andyp(a)parallax.co.uk> * redisplay-msw.c (mswindows_output_string) (mswindows_output_string): output the background pixmap if we have one.

1 participants
0 comments

[Near success] 21.0 "Repartida-pre1" XEmacs Lucid (beta38) on i3 86-pc-cygwin32 25 years, 12 months

Michael Hill

This report was copied and pasted from XEmacs (menubar only; the toolbar gives 'emacs does not own the primary selection'). The file dialog box hasn't worked since the advent of the msw toolbar, invoked either from the toolbar or from the menubar. 'make' failed at this point: Loading /binary/xemacs-21.0-b37/src/../lisp/update-elc.el... Loading find-paths.el... (14224) Loading packages.el... (22484) Loading setup-paths.el... (5444) Loading dump-paths.el... (0) Loading /binary/xemacs-21.0-b37/src/../lisp/dumped-lisp.el... (76) Loading /usr/local/packages/lisp/ediff/dumped-lisp.el... (0) Loading /usr/local/packages/lisp/efs/dumped-lisp.el... (0) Loading /usr/local/packages/lisp/tooltalk/dumped-lisp.el... (28) Loading /usr/local/packages/lisp/vc/dumped-lisp.el... (0) Loading /usr/local/packages/lisp/vm/dumped-lisp.el... (0) MAKE='make' EMACS='./src/xemacs' sh /binary/xemacs-21.0-b37/lib-src/update-elc.s h make: *** [all-elc] Error 1 bash-2.01$ cd src bash-2.01$ ./xemacs & [1] 9314 bash-2.01$ hence XEmacs won't install. Does 'Load .emacs' in the menubar have any function other than to switch from the splash page to the scratch buffer? If not, then it works perfectly, and I find that it's now the method I use most often to perform this function. After that I type 'M-w load-file RET ~/.emacs.' Mike > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /binary/xemacs-21.0-b37/Installation: > (Output from most recent run of ./configure) uname -a: CYGWIN32_NT DILBERT 4.0 19.1 i686 unknown ./configure '--site-includes=/usr/local/include' XEmacs 21.0-b38 "Repartida-pre1" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /binary/xemacs-21.0-b37 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/cygwin32.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O2 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? default What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6.3/include Where do we find X Windows libraries? /usr/X11R6.3/lib Additional header files: /usr/local/include Compiling in support for XAUTH. Compiling in support for XPM images. 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 support for GNU DBM. Compiling in support for ncurses. Compiling in File coding support. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. 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: --------------------------------------------------------- > /binary/xemacs-21.0-b37/beta.err does not exist!

1 participants
0 comments

Re: [CRASH] continued 25 years, 12 months

Paul Foley

On 29 Apr 1998 15:07:18 +0900, P E Jareth Hein wrote: > A first glance says massive memory corruption in the widget chain. > You said this was from reading mail, right? Have you applied the > patch I posted yesterday (related to image cleanups)? I have a hunch > that will fix your problem. If not, please let me know. No, your patch is in there[1]. There's something magical about my mail.xemacs folder, though, since I can read anything else without problems. The crash only occurs when I make a new frame -- I can read mail.xemacs, and continue using it for hours without trouble, as long as I stick to the frame(s) I've already got. I thought it may have been related to the Japanese text in one of the mail headers in mail.xemacs, so I removed that message and tried again. Still crashes. Footnotes: [1] Assuming you mean the one you sent under the message ID <ohvhrurxjn.fsf(a)pentagana.camelot.jp> -- Paul Foley <mycroft(a)actrix.gen.nz> --- PGP-encrypted mail preferred PGP key ID 0x1CA3386D available from keyservers fingerprint = 4A 76 83 D8 99 BC ED 33 C5 02 81 C9 BF 7A 91 E8

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