September 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Hrvoje Niksic

Lars Magne Ingebrigtsen <larsi(a)gnus.org> writes: > From what I gather, a char-table is a vector that has more than one > slot. (Kinda like an obarray, but not.) Strange. Under XEmacs, a char-table is exactly that: a char-table. It maps characters to values. It does so efficiently for large numbers of characters (in the Mule case) by using ranges. > So I've now modified parse-time to just use a vector instead. > Perhaps it was an effeciency issue? Are char tables meant to be > more efficient than vectors? Under Mule, there is not a chance in hell that you can use vectors to reference all the 2^19 characters. This is why char-tables were invented in the first place. All of this should be irrelevant in the specific case of parse-time, since it doesn't have to deal with wide chars. > Anyway, I can now use parse-time under XEmacs as well, which means > that the Gnus date handling functions are several magnitudes faster > than they used to be back when they used timezone.el to fiddle with > dates. Cool! -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- * Q: What is an experienced Emacs user? * A: A person who wishes that the terminal had pedals.

1 participants
0 comments

Re: make-char-table? 25 years, 8 months

Lars Magne Ingebrigtsen

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Uh, I really don't understand what the code above is supposed to do. > The FSF Emacs Lisp manual seems a bit unclear: > > Each char-table has a "subtype" which is a symbol. In order to be a > valid subtype, a symbol must have a `char-table-extra-slots' property > which is an integer between 0 and 10. This integer specifies the > number of "extra slots" in the char-table. > > What does this mean? What are the "extra slots" good for, and why is > the code above setting them to zero? I'm baffled! >From what I gather, a char-table is a vector that has more than one slot. (Kinda like an obarray, but not.) And parse-time used creates a char-table with 0 extra slots, which means that it's just an ordinary vector. Or something. So I've now modified parse-time to just use a vector instead. Perhaps it was an effeciency issue? Are char tables meant to be more efficient than vectors? Anyway, I can now use parse-time under XEmacs as well, which means that the Gnus date handling functions are several magnitudes faster than they used to be back when they used timezone.el to fiddle with dates. -- (domestic pets only, the antidote for overdose, milk.) larsi(a)ifi.uio.no * Lars Magne Ingebrigtsen

1 participants
0 comments

Re: make-char-table? 25 years, 8 months

Hrvoje Niksic

Lars Magne Ingebrigtsen <larsi(a)ifi.uio.no> writes: > parse-time.el uses the following: > > (put 'parse-time-syntax 'char-table-extra-slots 0) > (defvar parse-time-syntax (make-char-table 'parse-time-syntax)) > > I haven't really read up on char tables, but is there any way to do > something similar under XEmacs? Uh, I really don't understand what the code above is supposed to do. The FSF Emacs Lisp manual seems a bit unclear: Each char-table has a "subtype" which is a symbol. In order to be a valid subtype, a symbol must have a `char-table-extra-slots' property which is an integer between 0 and 10. This integer specifies the number of "extra slots" in the char-table. What does this mean? What are the "extra slots" good for, and why is the code above setting them to zero? I'm baffled! -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- The end of the world is coming... SAVE YOUR BUFFERS!

1 participants
0 comments

[OK] 21.0 "Irish Goat" XEmacs Lucid on i586-pc-linux 25 years, 8 months

Larry Ayers

Patched up from b54, built with egcs-1.1a. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/src/xemacs-21.0-b55/Installation: > (Output from most recent run of ./configure) uname -a: Linux liatris 2.1.120 #9 Sat Sep 5 07:51:38 CDT 1998 i586 unknown ./configure '--prefix=/usr/local/xemacs-beta' '--with-site-lisp' '--package-path=/usr/local/xemacs-beta/lib/xemacs/packages' '--with-toolbars=no' '--gung-ho' '--with-xpm' '--with-tiff=no' '--with-dialogs=athena' '--error-checking=none' '--debug=no' '--with-pop' XEmacs 21.0 "Irish Goat" configured for `i586-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21.0-b55 What installation prefix should install use? /usr/local/xemacs-beta 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/X11/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 PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). 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 POP for mail access Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. > Contents of /usr/local/src/xemacs-21.0-b55/beta.err > keeping lines matching > "^--\[\[\|\]\]$\|make\[\|error\|warn\|pure.*$space\|size$\|hides\b\|strange\|shadowings\|^Compilation\|not\s-+found" > and then deleting lines matching > "confl.*with.*auto-inlining\|/usr/local/src/xemacs-21\.0-b55/lisp/[^ ]+ hides " /usr/local/src/xemacs-21.0-b55/lib-src/etags.c:1849: warning: array subscript has type `char' /usr/local/src/xemacs-21.0-b55/lib-src/etags.c:1849: warning: array subscript has type `char' /usr/local/src/xemacs-21.0-b55/lib-src/etags.c:1849: warning: array subscript has type `char' /usr/local/src/xemacs-21.0-b55/lib-src/etags.c:1849: warning: array subscript has type `char' /usr/local/src/xemacs-21.0-b55/lib-src/ootags.c:1912: warning: array subscript has type `char' /usr/local/src/xemacs-21.0-b55/lib-src/ootags.c:1912: warning: array subscript has type `char' events.c:637: warning: unused variable `f' search.c:2265: warning: `prev' might be used uninitialized in this function glyphs-x.c:125: warning: `qtable' might be used uninitialized in this function redisplay-x.c:2256: warning: implicit declaration of function `poll' Purespace usage: 98300 of 1507600 (7% -- 1376k wasted). Purespace usage: 759968 of 1507600 (50% -- 730k wasted). XEmacs: Pure size adjusted, Don't Panic! I will restart the `make' make[1]: [xemacs] Error 1 (ignored) Purespace usage: 759968 of 759968 (100%). /usr/local/xemacs-beta/lib/xemacs/site-lisp/tex-site hides /usr/local/xemacs-beta/lib/xemacs/packages/lisp/auctex/tex-site

1 participants
0 comments

make-char-table? 25 years, 8 months

Lars Magne Ingebrigtsen

parse-time.el uses the following: (put 'parse-time-syntax 'char-table-extra-slots 0) (defvar parse-time-syntax (make-char-table 'parse-time-syntax)) I haven't really read up on char tables, but is there any way to do something similar under XEmacs? -- (domestic pets only, the antidote for overdose, milk.) larsi(a)ifi.uio.no * Lars Magne Ingebrigtsen

1 participants
0 comments

Re: Problems with first time V21 Installation attempt 25 years, 8 months

Michael Sperber

>>>>> "Lev" == Levent N Atasoy <Levent.Atasoy(a)macsch.com> writes: Lev> I downloaded and built 21.0 "Finnish Landrace" on my HP. Things went OK in Lev> general, but I wanted to note a couple of problems in case they are not known: Lev> 1. Somehow the Info-directory-list missed the info under xemacs-packages and Lev> site-packages and Details, please. In particular, I need the configure command line, the actual location of your package hierarchy, and the actual values of `Info-directory-list', `emacs-root' and `late-packages'. Lev> instead contained the following two directories as extras: Lev> "/usr/local/info/site-info" "/usr/local/info" The latter is to be expected. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

2 participants
1 comments

[URGENT PATCH] Visual package installer 25 years, 8 months

Darryl Okahata

[ Steve: Sorry about cc'ing you, but you want to make the final release ASAP, and so I'm sending you a copy to bypass any delays in the xemacs-patches queue. ] This patch is against B55 ("Irish Goat"). Basically, B55 contains the visual package installer patches that I submitted and subsequently withdrew. I submitted a fixed set (against *B54*) yesterday, but they apparently didn't make it through the queue. These patches fix B55 to bring it to the same fixed state, as applying my fixed patches (yesterday's) to B54 would would do. Here are combined xemacs-21.0/lisp and xemacs-21.0/man ChangeLogs: =============================================================================== 1998-09-06 Darryl Okahata <darrylo(a)sr.hp.com> * package-get.el: Fixed broken EFS downloading. Also, look for .tar.gz files first, in preference over .tgz files. * package-ui.el: Fix display of package version numbers. 1998-09-03 Darryl Okahata <darrylo(a)sr.hp.com> * packages.texi: Document manually installing binary packages. =============================================================================== -- Darryl Okahata darrylo(a)sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.

1 participants
0 comments

[Success] Irish Goat 25 years, 8 months

Rebecca Ore

Built with three fresh tarballs and one package I hadn't picked up before (elisp). Here's the installation file: uname -a: Linux ogoense.net 2.0.35 #1 Thu Jul 23 14:01:04 EDT 1998 i586 unknown ./configure '--with-mule=yes' XEmacs 21.0 "Irish Goat" configured for `i586-pc-linux'. Where should the build process find the source code? /home/rebecca/xemacs-21.0-b55 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 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 support for X-Face message headers. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. 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.

1 participants
0 comments

flyspell package? 25 years, 8 months

Lars Magne Ingebrigtsen

I've taken to using flyspell under Emacs 20, and I really like it. (It highlights things I've misspelled and stuff.) Has it been ported to XEmacs (if any porting is needed), and could a package be made for XEmacs 21? -- (domestic pets only, the antidote for overdose, milk.) larsi(a)ifi.uio.no * Lars Magne Ingebrigtsen

3 participants
2 comments

Re: FreeBSD 3.0, ELF and XEmacs 25 years, 8 months

SL Baur

Josh Howard <jrh(a)zeppelin.net> writes in xemacs-beta(a)xemacs.org: > While there's no actual reference to changes in unexelf, that I can > see, in the ChangeLog, it seems that synching that up with Emacs 20.3 > lets XEmacs compile and run peachy keen. I suppose I could simply diff > out what's changed and pick out the bits which helped this particular > problem, but I think that there were enough changes that maybe > somebody should just look it over and see what other platforms might > benefit from it. Our resident BSD expert is IENAGA Kazuyuki. Kazz? > SL Baur <steve(a)xemacs.org> writes: >> Josh Howard <jrh(a)zeppelin.net> writes in xemacs-beta(a)xemacs.org: >> >> > FreeBSD 3.0-CURRENT (soon to be -RELEASE) has switched from a.out to >> > ELF and XEmacs won't build or run properly. If s/freebsd.h is synched >> > up with Emacs 20.3, to use unexelf.c for instance, it will build >> > properly, but dumps core when it attempts to run. Moreover, Emacs-20.3 >> > builds and runs perfectly fine in the new ELF world of FreeBSD. >> > This is with 21.2, though I imagine all versions would have this same >> > problem. Here's a backtrace: >> >> In addition to changing s/freebsd.h, you might also grep the FSF >> ChangeLogs for other related changes. Was unexelf.c changed, for >> example?

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