December 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Hrvoje Niksic

Andy Piper <andyp(a)parallax.co.uk> writes: > At 22:05 03/12/98 -0800, Kyle Jones wrote: > >I have a feeling that if we could get lstreams from between > >XEmacs and the disk, I/O would be considerably faster. Loading > >Lisp, loading files, saving files, everything. So I'm glum > >about coding systems, since that requires the lstreams. > > Do they always come between xemacs and the disk? Could we optimise the > 'binary coding-system to do something sneaky? Also, I don't see why lstreams would have to be slow when they do nothing smart. For instance, why should a single (unchained) lstream be slower than stdio? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- The meta-Turing test counts a thing as intelligent if it seeks to devise and apply Turing tests to objects of its own creation.

3 participants
2 comments

Re: the splash buffer 25 years, 11 months

Adrian Aichner

>>>>> "Didier" == Didier Verna <verna(a)inf.enst.fr> writes: Didier> One day, my artistic pulse that some of you already know took Didier> control Didier> of my brain and I wrote a new splash buffer, wonderful, with lots of ascii Didier> art, everything beautifuly aligned, flowers and .... and this couldn't be Didier> used Didier> because proportional fonts would have fucked up everything. Didier> Today, for some reason, I didn't feel like writing my Ph.D., so I Didier> rewrote a new splash buffer. This one will work in all configurations, Didier> doesn't Didier> take more space than the old one, but is much much more readable, I think. Didier> I've made a screenshot at http://www.infres.enst.fr/~verna/splash.gif w3 doesn't display it. It shows the GIF data in binary form. emacs-version "21.2 \"Aglaophonos\" XEmacs Lucid (beta4)" w3-version "WWW 4.0pre.23 1998/04/17 19:06:08" However, the infamous "Internet Exploder" shows the page fine. The page looks a lot clearer than the current splash screen. I like it. Adrian Didier> What do you think ? Didier> -- Didier> / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ Didier> - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr Didier> /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 Didier> 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19 -- Adrian Aichner European Design Center Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

3 participants
2 comments

Re: 21.2.5 crash and question 25 years, 11 months

Mike McEwan

Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: > Please wait till Martin comments on this, I *really* have no idea what > is going on here -- this is one of my "zero-knowledge patches"! I have > not even read the new stuff in the internals manual. Well, *has* Martin commented? -- Mike.

2 participants
1 comments

[Failure] XEmacs 21.2-b5 "Aphrodite", i386-pc-win32 25 years, 11 months

Adrian Aichner

Next failure is a series. Seems to point to following src\ChangeLog 1998-11-30 Martin Buchholz <martin(a)xemacs.org> > XEmacs Build Report as generated > by build-report-version $Revision: 1.53 $ follows: > Contents of c:\export\home\tmp\21.2\xemacs\nt\Installation: > (Output from most recent run of ./configure)

2 participants
1 comments

[Failure] XEmacs 21.2-b5 "Aphrodite", i386-pc-win32 25 years, 11 months

Adrian Aichner

pure.c fails to compile due to a conflict between puresize.h and pure.c. Should get_PURESIZE be a function or a macro? Adrian > XEmacs Build Report as generated > by build-report-version $Revision: 1.53 $ follows: > Contents of c:\export\home\tmp\21.2\xemacs\nt\Installation: > (Output from most recent run of ./configure)

2 participants
1 comments

[Failure] XEmacs 21.2-b5 "Aphrodite", i386-pc-win32 25 years, 11 months

Adrian Aichner

..\src\frame-msw.c(131) : warning C4013: 'Fmake_hash_table' undefined; assuming extern returning int ..\src\frame-msw.c(132) : error C2115: '=' : incompatible types terminates compilation under WindowsNT native. Adrian > XEmacs Build Report as generated > by build-report-version $Revision: 1.53 $ follows: > Contents of c:\export\home\tmp\21.2\xemacs\nt\Installation: > (Output from most recent run of ./configure)

3 participants
3 comments

Re: xemacs-21.2.5 on Windows 25 years, 11 months

Adrian Aichner

>>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: Martin> As you are probably all aware, I have broken xemacs-21.2.5 on Windows, Martin> and I don't have a development environment on Windows. I'm Martin> particularly interested in getting at least a partial success story, Martin> so we can quickly release xemacs-21.2.6. Martin, you patch makes frame-msw.c compile perfectly under WindowsNT. Thanks! Next will be my [Failure] build report due to pure.c pure.c ..\src\pure.c(30) : warning C4002: too many actual parameters for macro 'get_PURESIZE' ..\src\pure.c(30) : error C2059: syntax error : 'constant' NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop. Adrian Martin> Here's the key patch again. Apply this, and let me know if you get a Martin> successful build. If you succeed, try `make check'. Martin> 1998-12-06 Martin Buchholz <martin(a)xemacs.org> Martin> * frame-msw.c (mswindows_init_frame_1): Martin> - use make_lisp_hash_table, not Fmake_hash_table Martin> - include elhash.h Martin> --- src/frame-msw.c.old Martin> +++ src/frame-msw.c Martin> ＠＠ -35,6 +35,7 ＠＠ Martin> #include "buffer.h" Martin> #include "console-msw.h" Martin> #include "glyphs-msw.h" Martin> +#include "elhash.h" Martin> #include "events.h" Martin> #include "faces.h" Martin> #include "frame.h" Martin> ＠＠ -128,8 +129,8 ＠＠ Martin> FRAME_MSWINDOWS_DATA(f)->sizing = 0; Martin> FRAME_MSWINDOWS_MENU_HASH_TABLE(f) = Qnil; Martin> #ifdef HAVE_TOOLBARS Martin> - FRAME_MSWINDOWS_TOOLBAR_HASH_TABLE(f) = Fmake_hash_table (make_int (50), Martin> - Qequal); Martin> + FRAME_MSWINDOWS_TOOLBAR_HASH_TABLE(f) = Martin> + make_lisp_hash_table (50, HASH_TABLE_NON_WEAK, HASH_TABLE_EQUAL); Martin> #endif Martin> /* Will initialize these in WM_SIZE handler. We cannot do it now,

2 participants
1 comments

trouble report: XEmacs 20.4 Mule SPARC doesn't work 25 years, 11 months

Ham Nguyen [Anh Yeu Dau]

Hi, Sorry if this goes to the wrong alias -- don't know where to post problem report likes this I'd like to report a problem against: xemacs-20.4-sparc-sun-solaris2.4-mule.tar.gz dated March 1, 1998, posted at: ftp://ftp.xemacs.org/pub/xemacs/xemacs-20.4/binary-kits/sunos5/ On startup, it complains about my XEmacs binaries are in a strange place then quit. I followed its suggestion to set various EMACS* env vars to get it to work but couldn't. I ended up using the non-MULE version and that works fine! Also, MULE i386 version works fine too. thanks ha`m

1 participants
0 comments

Re: 21.2b4: why is late-package-load-path nil? 25 years, 11 months

Les Schaffer

Michael Sperber says: > At the very least, you need to move > /usr/lib/xemacs/site-lisp > to > /usr/lib/xemacs/site-packages/lisp ^^^^^ this seems to do the trick fine, and now i can start using 21.2b4 > This is not the way to go---site-lisp and site-packages are > different beasts. site-packages is a package hierarchy. (Read > about their layout in the texinfo documentation.) To get site-lisp > back, specify --with-site-lisp (I think) from configure. i saw the --with-site-lisp stuff in configure, but i figured since this was a depracated way of doing business, i oughta find out how to do it right. well, what is the right way to do what used to be the old site-lisp dir hierarchy? is it as above? i read (quickly) through the NEWS stuff and i wouldnt say it popped right out at me. (YMPV) -- ____ Les Schaffer godzilla(a)netmeg.net ___| --->> Engineering R&D <<--- Theoretical & Applied Mechanics | Designspring, Inc. Center for Radiophysics & Space Research | Westport, CT USA Cornell Univ. schaffer(a)tam.cornell.edu | les(a)designspring.com

1 participants
0 comments

Re: What to build? 25 years, 11 months

Raymond Toy

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: >> Oh well. I'll just have to wait for the powers that be to make a >> tarball. It's not like everyone is dying for me to test out the >> latest stuff. :-) I've haven't been nearly as active as I used to >> be. :-( sb> There's going to be 21.2.5 tarballs released in the next few hours. sb> There aren't likely to be 21.2 tarballs released again until April sb> unless a miracle happens. Actually I was asking about 21.0 tarballs. I assume that would be released before 21.2 tarballs. The 21.2.x tarball works just fine on my machine, by the way. Ray

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 December 1998