April 1998 - XEmacs-Beta - XEmacs Mailing List Archives

[Success] 21.0 "Pygmy" XEmacs Lucid (beta37) on hppa1.1-hp-hpux9.05 26 years, 5 months

Pekka Marjola

> XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /tools/contrib/beta/src/xemacs-21.0-b37/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

[OK] 21.0 "Pygmy" XEmacs Lucid (beta37) on sparc-sun-solaris2.5 26 years, 5 months

Didier Verna

> XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /inf/metheny/latest/xemacs-21.0-b37/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

Re: SIGSEGV in alloc.c 26 years, 5 months

Andreas Jaeger

Hi Richard, that looks like the same problem Martin, Michael and myself are experiencing. A backtrace (type "bt" in gdb) would show if this is really the case. A workaround is according to Michael to add -fno-expensive-optimizations to the compiler flags. Martin mailed another workaround for this problem (see his email with subject "[Patch]: latest egcs + mule") and contacted the egcs developers. Until they fix egcs (it seems to be a bug in egcs), you've to use one of the workarounds. There's nothing else that can be done AFAIK at the moment (except fixing egcs;-). Andreas -- Andreas Jaeger aj(a)arthur.rhein-neckar.de jaeger(a)informatik.uni-kl.de for pgp-key finger ajaeger(a)alma.student.uni-kl.de

1 participants
0 comments

[PATCH] msw / toolbar cleanup 26 years, 5 months

Andy Piper

This consolidates toolbar hastables, removes warnings and enables the new process code under cygwin which seemed to have slipped through the net last time. andy Fri Apr 24 19:38:19 1998 Andy Piper <andyp(a)parallax.co.uk> * configure.in: check for our special select in msw. Fri Apr 24 19:38:19 1998 Andy Piper <andyp(a)parallax.co.uk> * config.h.in: support our special select * event-msw.c: * toolbar-msw.c: * console-msw.h: toolbar cleanup. * device-msw.c: * emacs.c: * frame-msw.c: * glyphs-msw.h: * ntplay.c: * process-unix.c: * select-msw.c: * sheap.c: * s/cygwin32.h: warning elimination.

2 participants
1 comments

Re: stupid question... 26 years, 5 months

Jens Lautenbacher

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > >>>>> "Jens" == Jens Lautenbacher <jens(a)tellux.de> writes: > > Jens> Sorry if this is a faq or plain stupid, but I simply seem to be unable > Jens> to get an xemacs-21 beta working... > > Jens> After a long time I want to again work a bit with xemacs, and so I > Jens> decided to get a new package enabled xemacs-21. I downloadded the cvs > Jens> xemacs-20 and xemacs-packages. > > Are you on xemacs-beta? You should be. > I'll send you Steven latest beta announcement, in case you aren't. > I will answer most of your questions. > > Jens> But what now? > > Jens> I first compiled xemacs and installed, then went on tho the packages > Jens> and also compiled these... but where am I supposed to install them? Do > Jens> I simply link the whole structure under (prefix)/lib/xemacs/packages? > Jens> That's the default path for packes if I read the docs right... > > Jens> But do I have to redump XEmacs? How will it know about the packages? > > Use --package-path option to configure. I did :-(

2 participants
1 comments

Re: Scrolbars back to 15 pixels 26 years, 5 months

Didier Verna

"Kirill M. Katsnelson" <kkm(a)kis.ru> writes: > An evil something worked back 3 pixels to scrollbar thickness in my > installation. Specification is set globally. Didier's scrollbar visible > option did the trick, right? probably. > We DEMAND a separate specifier for scrollbar visibility. Oh we do! No? :) Yes we do ! :-) >> (defcustom scrollbars-visible-p >> [...] >> ;; This is really a hack: there should be a real specifier for this, in >> ;; order to turn on/off the scrollbars without altering their size. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Re: What's the beast "untabify"? 26 years, 5 months

Didier Verna

"Kirill M. Katsnelson" <kkm(a)kis.ru> writes: > Some lisp code refers to this function, even xemacs-base, but > it is not around. In which package is it? > > Kirill `untabify' is an interactive compiled Lisp function -- loaded from "tabify" (untabify START END) Documentation: Convert all tabs in region to multiple spaces, preserving columns. Called non-interactively, the region is specified by arguments START and END, rather than by the position of point and mark. The variable `tab-width' controls the spacing of tab stops. M-x locate-library untabify => text-modes/tabify.elc -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

crypt -- where 26 years, 5 months

Marcus Thiessel

I think the time has come to switch myself over to XEmacs 21.0 to daily business. In my usual setup I used to use crypt. Where has it gone!? --Marcus

1 participants
0 comments

[Success] 21.0 "Pygmy" XEmacs Lucid (beta37) on hppa1.1-hp-hpux11.00 26 years, 5 months

Marcus Thiessel

>From scratch with no problems. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /opt/src/xemacs-21.0-b37/Installation: > (Output from most recent run of ./configure) uname -a: HP-UX tmbbwtx B.11.00 A 9000/720 16954192 two-user license ./configure 'hppa1.1-hp-hpux11.00' '--dynamic=no' '--prefix=/usr/local/xemacs' '--with-x' '--with-dialogs=motif' '--with-xface=yes' '--with-tty=yes' '--x-includes=/usr/include/Motif1.2_R6 -I/usr/include/X11R6' '--x-libraries=/usr/lib/Motif1.2_R6 -L/usr/lib/X11R6' '--with-database=dbm' '--with-pop' '--mail-locking=lockf' '--site-includes=/usr/contrib/include -I/usr/local/include' '--error-checking=none' '--extra-verbose' '--site-libraries=/usr/contrib/lib -L/usr/local/lib' '--with-sound=no' '--with-xmu' '--with-mule=yes' '--with-cde=yes' '--with-session' '--with-tooltalk=yes' '--with-gcc=no' '--with-gnu-make=no' '--gung-ho' '--package-path=/opt/src/packages' '--cflags=+DA1.1 +DD32 +O2 +Onolimit +Odataprefetch +Oentrysched +Oprocelim +Olibcalls' XEmacs 21.0-b37 "Pygmy" configured for `hppa1.1-hp-hpux11.00'. Where should the build process find the source code? /opt/src/xemacs-21.0-b37 What installation prefix should install use? /usr/local/xemacs What operating system and machine description files should XEmacs use? `s/hpux11.h' and `m/hp800.h' What compiler should XEmacs be built with? cc -Ae +DA1.1 +DD32 +O2 +Onolimit +Odataprefetch +Oentrysched +Oprocelim +Olibcalls 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/include/Motif1.2_R6 -I/usr/include/X11R6 /usr/contrib/X11R6/include Where do we find X Windows libraries? /usr/dt/lib /usr/lib/Motif1.2_R6 -L/usr/lib/X11R6 /usr/contrib/X11R6/lib Additional header files: /usr/contrib/include -I/usr/local/include Additional libraries: /usr/contrib/lib -L/usr/local/lib 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 support for DBM. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using Motif to provide XIM support. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in support for 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 "lockf" for locking mail spool files. Using POP for mail access Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. > /opt/src/xemacs-21.0-b37/beta.err does not exist!

1 participants
0 comments

Re: Comparison between integer and character is constant nil (?\; and 0) 26 years, 5 months

SL Baur

[Cc'ing back to xemacs-beta] Paul Foley <mycroft(a)actrix.gen.nz> writes: > On 26 Apr 1998 18:01:49 -0700, SL Baur wrote: >>> Comparison between integer and character is constant nil (?\; and 0) >>> [fume-find-next-c-function-name, funcall, ... >> from `fume-find-next-c-function-name' in func-menu.el. >> `following-char' returns integer 0 when the end of the buffer is >> reached. This used to lose when integer 0 was indistinguishable from >> the character NUL, but now it doesn't. You may safely ignore this >> message. > So it's OK when it occurs due to end-of-buffer, but I assume it's a > Bad Thing when comparing non-zero-valued characters? More or less. The usual cause of an Ebola notice at the beginning or end of a buffer is due to use of preceding-char and following-char. Those functions return integer 0 at the boundary. Since they really want to return something that cannot be a character, this is O.K. Kind of yucky, but O.K. We have replacement functions `char-after' and `char-before' that return nil at buffer boundaries, but they're not really needed except for pedants. In general, an Ebola notice of a comparison of a character and integer 0 when generated from usage of preceding-char and following-char is not Ebola and is safe usage. > I've been getting these things from SKK -- when the SKK tutorial > hits the line > ;; (skktut-today) > one "Ebola" notice occurs, and every time I enter okurigana on a word, > a notice occurs. [These are with non-zero values.] That might well be Ebola. Please post the notices you are getting. If you can figure out which file they are coming from, evaluate that file in an XEmacs buffer and repeat the action that caused the notice -- the stacktraces will be that much better. > You said >> It's an Ebola notice. Characters used to be equivalent to integers >> and now they are not. This causes code like (eq ?A 65) which used to >> return t in XEmacs 19 (and FSF Emacs) to now return nil. > but this loses if you really want to compare ?A and integer 65, yes? That's correct. > Implies a porting problem? Yup. > [Is it correct to use (eq (char-int ?A) 65)?] Yes. It is also _incorrect_ (and Ebola) to do something like (eq ?B (1+ ?A)). Arithmetic on characters is allowed, but turns the characters into integers. You would have to do (eq ?B (int-char (1+ ?A))) to make it work right.

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