March 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: A real database for Emacs 24 years, 1 month

SL Baur

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: > SL Baur <steve(a)beopen.com> writes: >> Attached are patches to XEmacs 21.1.10 to add runtime support for the >> PostgreSQL relational database. > Did mean for this to go to -patches? Or did you send it here because > it still preliminary.. > Three comments... > 1. Can we have this as a module pleeeze? Is the module code stable now? And, are modules built by default? Personally, I'd prefer it not being a module by default, because libpq is lightweight and linked shared by default and the Lisp binding is lightweight (~13k with full debugging enabled). > 2. >> Note: This entry point is provided for completeness, but its use is not >> recommended. The preferred way to delete connections is to let the Emacs >> garbage collection mechanism do it. > Isn't this bad in the same way that closing files by finalization is? The same issue exists on cleaning up PGresult variables. In my testing, calling `pq-final' was an insta-crash. How do I do this correctly? Can I force PGconn and PGresult variables to never be copied? > 3. The harlequin M-BS xanalysis common lisp SQL bindings allow > iterating over the result of a query using map- and do- like > functions. IIRC they do this not by downloading all the results but > by transparently creating a database cursor[1] for you. That would > be very cool. I'm providing a low-level, policy-free binding to the library. This functionality can be done easily in additional Lisp code. I got asynchronous queries[1] working last night. Cursors should work for free since they're implemented by the Postgres backend in SQL. I'll try that this afternoon. > Footnotes: > [1] I think cursor is the correct term. It is. Footnotes: [1] The don't buy near as much as I hoped due to unexpected apparent utter brain damage in the XEmacs event code.

2 participants
1 comments

Re: Modules (was: Re: How about a feature freeze) 24 years, 1 month

Jan Vroonhof

john s jacobs anderson <jacobs(a)xemacs.org> writes: > In order to really be attractive, I think Jan's suggestion would need > to be accompanied by a mp3 player mode, and the inclusion of one or > more of the IM/chat modes in the standard tarball. There already have UDP support in XEmacs 21.2 to support eicq and there are several mp3 control programs in elisp. I haven't seen an mp3 decode in elisp yet. Jan

3 participants
2 comments

[FAIL] 21.2 from CVS 24 years, 1 month

Norbert Koch

Hi! After updating from CVS I get the following error: /usr/X11R6/include linuxplay.c linuxplay.c:64: `#include' expects "FILENAME" or <FILENAME> *** Error code 1 The compiler chokes on the following line: #include SOUNDCARD_H_FILE /* Path computed by configure */ Looks like the file hasn't been inserted. To be honest, I don't know, why it tries to compile linuxplay.c at all, because (7):xemacs$ uname -a FreeBSD sokrates 3.2-RELEASE FreeBSD 3.2-RELEASE #6: Sat Nov 13 10:57:32 CET 1999 root＠sokrates:/usr/local/src/sys/compile/NKAAAA i386 Any hints? Thanks, norbert. -- .. Should I get locked in the PRINCIPAL'S OFFICE today -- or have a VASECTOMY??

3 participants
2 comments

Re: cannot start beta32 24 years, 1 month

Colin Rafferty

Andy Piper writes: > At 09:13 AM 3/27/00 -0500, Colin Rafferty wrote: >> Running an IRIX or Linux build, I get this with the display either on >> Solaris or Linux (AccelX X server). > Are you using LessTif on Linux? Looks like I need to install it... I'm sorry. On Linux, I have no motif/lesstif. At the moment that I sent my previous email, my Linux box was down, so I only sent Installation from IRIX. Linux looks like this: uname -a: Linux malaria 2.2.5-15 #1 Mon Apr 19 23:00:46 EDT 1999 i686 unknown /ms/user/c/craffert/proj/shadow/xemacs/xemacs-21.2.32/configure '--pdump' '--compiler=/usr/bin/cc' '--with-png=yes' '--extra-verbose' '--package-path=/ms/user/c/craffert/.xemacs::/ms/dev/fsf/xemacs/sumo-19990729/install/common/:~/proj/shadow/xemacs/packages::/ms/dist/fsf/PROJ/xemacs/20.4.0/exec/lib/xemacs-20.4' XEmacs 21.2-b32 "Kastor & Polydeukes" configured for `i686-pc-linux'. Where should the build process find the source code? /ms/user/c/craffert/proj/shadow/xemacs/xemacs-21.2.32 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? /usr/bin/cc -g -O3 -Wall -Wno-switch -Wpointer-arith -Winline -Wmissing-prototypes -Wshadow 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? no 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/X11/lib Athena library to link: Xaw Athena header include path: X11/Xaw 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 Enlightened Sound Daemon (ESD). Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Athena native widgets. Using Athena dialog boxes. Compiling in dynamic shared object module support. movemail will use "dot-locking" for locking mail spool files. Using the new portable dumper. Compiling in extra code for debugging. 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: --------------------------------------------------------- -- Colin

1 participants
0 comments

Loadable modules 24 years, 1 month

Kean Johnston

All, Well, its been a hectic 9 months, but I am now able to dedicate more of my time to the two projects I care most about, XEmacs and XFree86. I am glad to say that I now have official sanction to work on these projects (as well as a few others) and that I can play a more active role than I have been. I also promise to read the mailing list every day, not every six months :-) As some of you know, I am the persopn responsible for inflicting the modules stuff on you all, and I understand there have been some problems with it, especially on some of the less common platforms. I would like to hear from anyone that is having a problem with the dynamic modules. Please make sure they are enabled by configuring with --with-modules. So, aside from beefing up platform support, I would like to start talking about how we can best use the module technology. Remember that the main aim is to provide the extensibility that users are accustomed to in Lisp, but at the C level (for speed more than anything else). Aside from moving some features from Lisp into C modules, I would like to know if we should consider extending the autoload mechanism to load in modules on demand, whether or not modules impose a security risk (I am guessing it is possible to do things with the system API that are not possible from within the Lisp reader), and how we will deal with platforms that dont support any form of dynamic module loading. This last issue (how to deal with systems that dont support modules) is the toughest issue that I can see. If modules are used properly, they can provide an incredible performance boost to the users. Lets be honest, NO Emacs wins great awards for speed, even though they are almost all "acceptably fast". So there is a real benefit to using modules, but it is unrealistic to expect package authors to maintain two sets of code (C for the module folks, Lisp for the rest). So, before we realistically start debating what to move into modules, we need to establish exactly which systems are afflicted with no module disease, and how important that is. I suspect that if it is limited to very old, very crufty versions of OSes that are relatively unpopular, that we can probably live with the limitation. If, on the other hand, popular platforms are affected, we are of course dead in the water, and modules will remain a relatively uncommon form of Emacs extension. So, given the list of platforms that are currently supported, how many of them would be adversely affected by a move to modules? If the maintainers of each different OS support code can tell me whether or not some form of dynamic loading technology exists on their platforms, I can draw up a matrix of what would be affected, and we can go from there. Having said all of that, I would like to throw out a list of potential cnadidates for migration to modules. I am hoping that at least some of the authors of these packages are also on this list, and can comment on the feasability (and desirability) of moving to modules. o SGML mode. The mode itself could easily remain in Lisp, but is it desirable to have some kind of SGML validation tool loaded as a module? Could SP be loaded in to the editor, and would this make it easier to have on-the-fly validation to make XEmacs a really hot SGML/XML editing environment? o W3. This is the most obvious candidate, and if memory serves, the author expressed interest at some stage in doing a module version. Its big, its slow, but its damn useful and the performance win would make a huge difference to the package. It wont be Mozilla, but then who wants that anyway? :-) o Several of the edit-utils packages, such as scroll-in-place, bookmark, etc, that are used frequently. mode-motion+ is another potential candidate. o Some of the base packages, such as comint, the byte compiler and optimizer, common lisp, font-lock, simple.el (why isnt this in C already?). Thew font-lock would be the biggest win, especially if it was possible to use a different scanner, rather than zillions of regexps, which are much slower than actual tokenization. o Start moving portions of the current C code into modules, so that they are only loaded on demand. For example, TTY support, X11 support, the LDAP and base64 stuff (which are already sample modules), possibly compile many differnt menu / dialog types so the user can select one at load time, etc. There are many ways we can use modules on existing C code. Basically, any package which is executed frequently, especially those at every keystroke or on motion outside of a line, would benefit greatly from being implemented in C. If other folks have other candidates, lets talk about them. Well, thanks for your patience with this long message. I hope we can start dialogue on this topic again, and actually move forward with it. It is a very useful addition to XEmacs (and I believe the FSF has picked up, or is going to pick up, the same stuff), so maybe modules will start playing more of a role in an Emacs's life. Peace and happy hacking to you all :-) Kean.

1 participants
0 comments

error with gutters/vm 24 years, 1 month

Jeff Miller

cvs'ed this afternoon. xemacs starts ok, but if i do M-x vm, i get: Gutter spec must be string, plist or nil: #<x-frame "emacs" 0x1fb4> Here is the backtrace from setting debug-on-error to t. jeff Signaling: (error "Gutter spec must be string, plist or nil" #<x-frame "emacs" 0x1fb4>) signal(error ("Gutter spec must be string, plist or nil" #<x-frame "emacs" 0x1fb4>)) byte-code("..." [kill-buffer buf signal data] 3) find-file-noselect("/home/jmiller/.mail/INBOX") byte-code("..." [bufferp folder nil preserve-auto-save-file totals-blurb first-time folder-buffer did-read-index-file full-startup expand-file-name vm-primary-inbox vm-folder-directory file file-directory-p error "%s is a directory" vm-get-file-buffer default-directory t no-conversion coding-system-for-read default-enable-multibyte-characters enable-local-variables inhibit-local-variables message "Reading %s..." find-file-noselect item vm-folder-history "Reading %s... done" vm-fsfemacs-mule-p enable-multibyte-characters set-buffer-multibyte buffer-file-coding-system current-load-list vm-xemacs-mule-p get-coding-system no-conversion-unix no-conversion-dos no-conversion-mac binary buffer-modified-p omodified buffer-read-only ((set-buffer-modified-p omodified)) encode-coding-region set-buffer-file-coding-system decode-coding-region coding-system-base ((set-buffer-modified-p omodified)) ...] 7) #<compiled-function (&optional folder read-only) "...(7)" [vm-session-initialization done (byte-code "À !?ÂÀ !« ªà ®É\n\"Í!«ÎÏ\"ªÇÐ!®Á«É!®ÒÂÓØÙ\"Ú! ®\n＠¬B)ØÝ\"-)q««àÂ!á\"B\"#«Åä!!äå!=¬»ä!!äæ!=¬±ä!!äç!=¬§ä!!äè!=¬Âé *+ìíed!#îÓÂ\"ïed!#+«±ð!!ðÓ!=¬§ð!!ðè!=¬Âé *+ñíed!#îÓÂ\"ïed!#+ò ó é ¬ô56÷=?8é ?ùú 8\"®;®üý!® += «þp!ÿô!＠

2 participants
3 comments

Bug-Report XEmacs crash: assertion failed, Fatal error (6) 24 years, 1 month

Ulrich Kaage

Hi, XEmacs 21.2 (beta32) "Kastor & Polydeukes" [Lucid] (sparc-sun-solaris2.6, Mule) of Mon Mar 27 2000 on inss24 "--prefix=/usr/users/kaage/lib/xemacs --dynamic=yes --with-dialogs=athena --with-site-lisp --with-mule" working with the XEmacs cvs version of today, xemacs crashed suddenly with Fatal error (6) while using VM and left the following message on the terminal: Fatal error: assertion failed, file glyphs.c, line 2917, EQ (Fgethash (instantiator, XWINDOW (domain)->subwindow_instance_cache, Qunbound), instance) Lisp backtrace follows: # (unwind-protect ...) # (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque-ptr, adr=0x2c586c) 0x331000> ...) # (unwind-protect ...) # bind (inhibit-quit) # (condition-case ... . error) # (catch top-level ...) GDB backtrace follows: (gdb) where #0 0xef10800c in _libc_kill () from /lib/libc.so.1 #1 0xa3bf8 in fatal_error_signal (sig=6) at emacs.c:293 #2 <signal handler called> #3 0xef10800c in _libc_kill () from /lib/libc.so.1 #4 0xef0ba4ac in abort () from /lib/libc.so.1 #5 0xa6534 in syms_of_emacs () at emacs.c:2754

2 participants
2 comments

Re: [PATCH for 21.[12]] Re: Can't install packages produced on WindowsNT 24 years, 1 month

Adrian Aichner

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: >> I will devise a patch for package-get.el and package-info.el to use >> insert-file-contents-literally if nobody objects. Jan> Perfect. However it needs my patch to Jan> insert-file-contents-literally to actually work (currently Jan> i-f-c-l does not set the coding system!) Hello Jan, is this a patch you have already submitted or commited? I haven't found it in xemacs-patches. Adrian Jan> Jan Jan> P.S. If all goes well I can actually apply patches from thursday or Jan> so. I am in the middle of moving. Thanks for the info. I had forgotten you're in the middle of moving. Hope all goes well.

1 participants
0 comments

Re: X sequence lost 24 years, 1 month

Michael Sperber

>>>>> "Andy" == Andy Piper <andy(a)xemacs.org> writes: Andy> At 06:37 PM 3/25/00 +0100, Michael Sperber [Mr. Preprocessor] wrote: >> >> I see the "async reply" problem mostly upon starting a subprocess, >> like igrep. Could this be related to Ben's subprocess changes? >> >> Xlib: unexpected async reply (sequence 0xd03)! >> Xlib: sequence lost (0x101c2 > 0xd03) in reply type 0x99! >> Xlib: sequence lost (0x10000 > 0xd03) in reply type 0x0! >> >> xemacs: X Error of failed request: 0 >> Major opcode of failed request: 3 (X_GetWindowAttributes) >> Serial number of failed request: 0 >> Current serial number in output stream: 3331 >> >> Anybody got any idea on how I can debug this? Andy> What happens if you do (x-debug-mode t) and then put a breakpoint in gdb in Andy> x_error_handler? Then, the bug doesn't occur anymore, at least as far as I can see. On the other hand, with (x-debug-mode t), all sorts of other things go wrong: Half the time, XEmacs can't save files. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: EFS 1.19 prerelease checked into CVS 24 years, 1 month

Michael Sperber

>>>>> "Andreas" == Andreas Jaeger <aj(a)suse.de> writes: >>>>> Michael Sperber writes: >> Subject pretty much says all. There aren't many changes since 1.18, >> but Jan's `insert-file-contents' changes are in there as well as a >> gross hack to support wu-ftpd 2.6.0 which is broken as usual. >> Andreas: I'd like there to be a 1-2 week period before this gets >> rolled into a new binary package. Andreas> Ok, I try to remember it - but the period might be a bit Andreas> longer. Longer is no problem. Andreas> The only problem which I do have is that I can't make a sumo Andreas> tar ball since otherwise efs would be part of the sumo tar Andreas> ball. I'm afraid I don't understand what you're saying here. You can't make a SUMO tarball *because* I checked in a new EFS? -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

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 March 2000