August 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Karl M. Hegbloom

>>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: >>>>> "Karl" == Karl M Hegbloom <karlheg(a)inetarena.com> writes: Karl> It's there... I have it installed, though this XEmacs is Karl> linked against `gifreader'. Stephen> It's not in hamm or bo. I assume that _you_ aren't Stephen> running rexx. So you must be on the development Stephen> branch.... Yes, that's right. "slink".

1 participants
0 comments

Re: [21.2] gnuserv doesn't exit when xemacs exits 27 years

Jan Vroonhof

giacomo boffi <boffi(a)rachele.stru.polimi.it> writes: > sorry for the delay. yes, if i start xemacs with nohup, gnuserv hangs > when xemacs is shut down Did you seen the patch I sent for this Jan P.S. If not here it is again Index: process-unix.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/src/process-unix.c,v retrieving revision 1.11 diff -u -u -r1.11 process-unix.c --- process-unix.c 1998/06/30 06:35:58 1.11 +++ process-unix.c 1998/08/20 21:19:22 ＠＠ -920,12 +920,14 ＠＠ EMACS_SET_TTY_PROCESS_GROUP (xforkin, &piddly); } -# ifdef AIX /* On AIX, we've disabled SIGHUP above once we start a child on a pty. Now reenable it in the child, so it - will die when we want it to. */ + will die when we want it to. + JV: This needs to be done ALWAYS as we might have inherited + a SIG_IGN handling from our parent (nohup) and we are in new + process group. + */ signal (SIGHUP, SIG_DFL); -# endif /* AIX */ } #endif /* HAVE_PTYS */

1 participants
0 comments

[Success] 21.0 "Erzgeberg" XEmacs Lucid on i686-pc-linux 27 years

Mauro Condarelli

A couple of "strange things" === 1 I had to configure with "LD_LIBRARY_PATH=/usr/local/lib ./configure" to avoid the following error: -------------------------------------------------------------------- WARNING: Compiling without PNG image support. Reason: PNG library version and header file don't match! WARNING: You should strongly consider installing the PNG libraries. WARNING: Otherwise certain images and glyphs may not display. WARNING: (a copy may be found in ftp://ftp.xemacs.org/pub/xemacs/aux) -------------------------------------------------------------------- - I'm using a fairly standard debian-hamm distribution. - I have libpng-1.0.1 installed from debian - I installed libpng-1.0.2 in /usr/local - I did *not* remove the old lib (in/usr/lib) to keep dselect happy Can someone divine what's wrong in my setup? === 2 Some minibuffer prompts (ediff-directories prompt for the directories to compare is a good example) flatly refuse to scroll when the end of line is reached. The cursor stays at the end of the line and I have either to type blindly or enlarge the window to see whet I'm typing. Minibuffer seems to know quite well there's something there and correctly keeps track of typed chars (it even puts the right-arrow in the last char if i put the cursor in some other window), but stays anchored to the beginning of the string. The cursor stays full (indicating not-at-end-of-line) and remains on the last char of the line. Blind insertion happens in "the right place" (not where the cursor is. This is a partcular nuissance when You have long prompts. This behaviour is present from several releases, I'm not sure when it began. Any idea? === 3 Thanks in Advance ! :) > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/src/cvs/xemacs/xemacs-21/Installation: > (Output from most recent run of ./configure) uname -a: Linux Thor 2.0.34 #1 Thu May 14 09:51:39 CEST 1998 i686 unknown ./configure XEmacs 21.0 "Erzgeberg" configured for `i686-pc-linux'. Where should the build process find the source code? /usr/local/src/cvs/xemacs/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 Runtime library search path: /opt/GNOME/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 native sound support. Compiling in support for Berkeley DB. Compiling in support for ncurses. 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. > /usr/local/src/cvs/xemacs/xemacs-21/beta.err does not exist!

1 participants
0 comments

Re: 28 bit ought to be enough for anyone. 27 years

Hrvoje Niksic

Marcus Thiessel <thiessel(a)bbn.hp.com> writes: > Hrvoje Niksic writes: > | > Would everything break if we link with GMP (a GNU multiple precision > | > library which is quite efficient) for the integer stuff? > | > | That would be cool, but it's a project definitely more complex than > | just "linking with GMP". > > I'll keep my fingers crossed. My last experience with GMP was we had > to fix a lot of compiler warnings. :-( If by this you imply that GMP is not actively maintained, then I'd say it is almost certainly not the right extension for XEmacs. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- HOW YOU CAN TELL THAT IT'S GOING TO BE A ROTTEN DAY: #15 Your pet rock snaps at you.

2 participants
1 comments

lesstif dialog-boxes too wide 27 years

Kai Haberzettl

I have lesstif 0.85.3 installed and XEmacs is compiled with-dialog-boxes=motif. The dialog-boxes i get, e.g. when exiting XEmacs by closing the window, are too wide and exceed the screen-size. This is probably a lesstif-problem, but maybe it should be mentioned in PROBLEMS. Kai

2 participants
1 comments

Re: 28 bit ought to be enough for anyone. 27 years

Hrvoje Niksic

Simon Josefsson <jas(a)pdc.kth.se> writes: > I find the 28 bit limit on integers to be extremely painful. Build 21.0 betas with `--with-minimal-tagbits'. It raises the 28-bit limit to 31-bit. > Would everything break if we link with GMP (a GNU multiple precision > library which is quite efficient) for the integer stuff? That would be cool, but it's a project definitely more complex than just "linking with GMP". -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- aibohphobia (ay' bo fo beeya): n. The fear of palindromes.

2 participants
1 comments

Re: Status of XEmacs under MS-Windows? 27 years

Adrian Aichner

>>>>> "Matt" == Matt Stupple <matts(a)tibco.com> writes: Matt> Adrian Aichner wrote: >> >> 2. Only 32 sub-processes can be created before restarting XEmacs. >> This makes ediff useless for more than 32 differences. >> Matt> I think we've fixed this one now - grab an up-to-date beta (53 is Matt> latest) and retry; I don't see the restriction anymore. Thanks Matt, for the hint! I tried ediff-buffers and got 43 diffs. Using [Success] 21.0 "Erzgeberg" XEmacs Lucid, windows-nt, i386-pc-win32 I was able to go through all of them. I even went back through all of them with no trouble. For people used to MicroSoft's hard limits all over their `Products' it should be a relief that we can even go beyond 64 ;-> -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 D-81673 MUENCHEN E-mail aichner(a)ecf.teradyne.com

1 participants
0 comments

28 bit ought to be enough for anyone. 27 years

Simon Josefsson

I'm sorry if this has been discussed before or is part of the let's-replace-elisp-thread I've mostly been skipping. Or if has already been implemented, I still use XEmacs 20.4 Very well. I find the 28 bit limit on integers to be extremely painful. Would everything break if we link with GMP (a GNU multiple precision library which is quite efficient) for the integer stuff? Or as a backwards compatible way, implement it as a library so we can do things like (require 'gmp), (gmp-add (gmp-pow 2 512) (gmp-pow 2 3842)) or something. To implement Kerberos 5 with strong encryption in elisp, this is almost a must-have. /s

1 participants
0 comments

Re: [21.2] gnuserv doesn't exit when xemacs exits 27 years

Jan Vroonhof

Glynn Clements <glynn(a)sensei.co.uk> writes: > > > 2 --- SIGHUP (Hangup) --- > > > 3 --- SIGCONT (Continued) --- > > > 4 <... select resumed> ) = -1 ENOSYS (Function not implemented) > > > > It is getting the SIGHUP but it is not dying... (Are signal handler > > settings preseverd over fork/xexec. > > According to Stevens[1]: > > a) All signal dispositions are inherited across a fork(). > > b) exec() resets any signal for which a handler is installed to its > default disposition. Any signal which was ignored remains so. Then that may be it. Since some betas XEmacs now lets SIGHUP to remain SIG_IGN when it was. However gnuserv SHOULD also die in that case. That is probably the real problem problem in that gnuserv gets its standard streams in a weird state. giacomo, can you reproduce the problem using nohup xemacs -f gnuserv-start & from an xterm ? Jan

2 participants
1 comments

Re: GIF without LZW 27 years

Karl M. Hegbloom

>>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: Stephen> But it's not going to be immediately available on any Stephen> platform besides Red Hat Linux, right? Debian Linux Stephen> doesn't seem to have it, anyway. It's there... I have it installed, though this XEmacs is linked against `gifreader'. Package: libungif3g Status: install ok installed Priority: optional Section: graphics Installed-Size: 47 Maintainer: Jim Pick <jim(a)jimpick.com> Source: libungif Version: 3.0-2 Replaces: giflib3g Provides: giflib3g Depends: libc6 Conflicts: libgif3g, libgif2, giflib3g Description: shared library for GIF images (runtime lib) This is a shared library for working with GIF images. . The libungif library is a specially modified version of giflib which is free of the Unisys LZW patent. It can read all GIFs, but only write uncompressed GIFs. If you need to be able to write compressed GIFs, you can install the non-free giflib packages instead (which may not be available on CD). % cat /var/lib/dpkg/info/libungif3g.list /. /usr /usr/doc /usr/doc/libungif3g /usr/doc/libungif3g/README /usr/doc/libungif3g/UNCOMPRESSED_GIF /usr/doc/libungif3g/copyright /usr/doc/libungif3g/NEWS.gz /usr/doc/libungif3g/changelog.Debian.gz /usr/lib /usr/lib/libungif.so.3.0.0 /usr/lib/libungif.so.3 /usr/lib/libgif.so.3.0 /usr/lib/libgif.so.3 Package: libungif3g-dev Status: install ok installed Priority: optional Section: graphics Installed-Size: 51 Maintainer: Jim Pick <jim(a)jimpick.com> Source: libungif Version: 3.0-2 Replaces: giflib3g-dev, giflib3g Provides: giflib-dev Depends: libc6-dev, libungif3g (= 3.0-2) Conflicts: giflib-dev, giflib3g-dev, libgif-dev, libgif3g-dev, libgif2-dev Description: shared library for GIF images (development files) This package contains header files needed to compile programs that use libungif. . The libungif library is a specially modified version of giflib which is free of the Unisys LZW patent. It can read all GIFs, but only write uncompressed GIFs. If you need to be able to write compressed GIFs, you can install the non-free giflib packages instead (which may not be available on CD). Package: libungif-bin Status: install ok installed Priority: optional Section: graphics Installed-Size: 441 Maintainer: Jim Pick <jim(a)jimpick.com> Source: libungif Version: 3.0-2 Replaces: giflib-bin Provides: giflib-bin Depends: libungif3g (= 3.0-2), libc6, xlib6g (>= 3.3-5) Conflicts: giflib-bin, libgif3-bin Description: programs to convert GIF images These are some programs that use libungif to convert images. . The libungif library is a specially modified version of giflib which is free of the Unisys LZW patent. It can read all GIFs, but only write uncompressed GIFs. If you need to be able to write compressed GIFs, you can install the non-free giflib packages instead (which may not be available on CD).

2 participants
1 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 August 1998