April 1998 - XEmacs-Beta - XEmacs Mailing List Archives

[PATCH] stat vs fstat revisited 26 years, 2 months

Kirill M. Katsnelson

XEmacs asks "file changed on disk, really edit?") Kirill 1998-04-27 Kirill M. Katsnelson <kkm(a)kis.ru> * fileio.c (Fwrite_file_contents_internal): Prefer stat() over fstat() back for Windows, where closing a file changes its modification time. Index: src/fileio.c =================================================================== RCS file: /var/cvsroot/ntxemacs/src/fileio.c,v retrieving revision 1.8 diff --unified=2 -r1.8 fileio.c --- src/fileio.c 1998/04/27 00:30:31 1.8 +++ src/fileio.c 1998/04/26 20:34:26 ＠＠ -3321,5 +3321,6 ＠＠ /* On VMS and APOLLO, must do the stat after the close since closing changes the modtime. */ -#if 1 /* !defined (VMS) && !defined (APOLLO) */ + /* As it does on Windows too - kkm */ +#if !defined (WINDOWSNT) /* !defined (VMS) && !defined (APOLLO) */ fstat (desc, &st); #endif ＠＠ -3339,6 +3340,5 ＠＠ } - -#if 0 /* defined (VMS) || defined (APOLLO) */ +#if defined (WINDOWSNT) /* defined (VMS) || defined (APOLLO) */ stat ((char *) XSTRING_DATA (fn), &st); #endif

1 participants
0 comments

Strokes stuff 26 years, 2 months

David Bakhash

I've just tested out strokes with a new algorithm that seems to be performing on-line Chinese character recognition at an accuracy of 75.9% on the task of recognizing characters from a set of 79 characters (about 60/79 is the ratio). Note that this is with characters that were written completely cursively, and with a mouse, on varying computers, all of varying speeds. This is good news. Bad news is that the recognition happens pretty slow (I'm ashamed to say that I've only been able to get it down to about 2 hours to recognize about 80 charcters, and that's with compiled Allegro CL running through the ACL interpreter). But I'll make it faster later. I think I can dump this to an executable. Anyway, I have hardly trained the system, and so things will get *a lot* better. Just wanted to tell you guys the good news. Anyway, even though I can port this all to Elisp, that would just be a crying joke, unless I figured out a way so that I could skip over lots of characters. but with multi.el (the matrix package), the algorithms can be contained in elisp. But they're all written recursively, and I noticed that the ACL compiler mentioned a lot of optimizations it did while compiling the code. Plus, the fact that it has a built-in multi-dimensional array type (which I think is reasonably easy to implement, and there's just no reason why XEmacs shouldn't have it, especially if we just take a first swing at it and ignore dynamic sizing and fill pointers). dave

1 participants
0 comments

SIGSEGV in alloc.c 26 years, 2 months

Richard Ketchersid

For info on my installation or system see attached files. I have been getting segfaults in the past few xemacs. Well I sat down and stepped through the source code until I found where it is happening. Here is the gdb output. I am not a programmer so I am not even going to try to figure this out. I see from the list that there may be others with this problem. Breakpoint 1, main (argc=???, argv=???, envp=???) at /usr/src/CVS/xemacs-20/src/emacs.c:1974 1974 { (gdb) s 700 4997 XSETINT (Vgc_message, 0); (gdb) s 4998 all_lcrecords = 0; (gdb) 4999 ignore_malloc_warnings = 1; (gdb) 5001 mallopt (M_TRIM_THRESHOLD, 128*1024); /* trim threshold */ (gdb) 5002 mallopt (M_MMAP_THRESHOLD, 64*1024); /* mmap threshold */ (gdb) 5007 init_string_alloc (); (gdb) init_string_alloc () at /usr/src/CVS/xemacs-20/src/alloc.c:2002 2002 DECLARE_FIXED_TYPE_ALLOC (string, struct Lisp_String); (gdb) init_alloc_once_early () at /usr/src/CVS/xemacs-20/src/alloc.c:5008 5008 init_string_chars_alloc (); (gdb) init_string_chars_alloc () at /usr/src/CVS/xemacs-20/src/alloc.c:2092 2092 first_string_chars_block = xnew (struct string_chars_block); (gdb) xmalloc (size=1) at /usr/src/CVS/xemacs-20/src/alloc.c:389 389 { (gdb) 390 void *val = (void *) malloc (size); (gdb) 392 if (!val && (size != 0)) memory_full (); (gdb) 394 } (gdb) Program received signal SIGSEGV, Segmentation fault. 0x4035e11c in memcpy () (gdb) __________________ Richard Ketchersid +++_/_/+++_/_/++ UC Berkeley, Logic Group ++_/_/_/++_/+_/+ Office: 846 Evans +_/+++ _/+_/_/++ uname -a: Linux genera 2.1.95 #2 Sat Apr 11 10:14:58 PDT 1998 i486 unknown /usr/src/CVS/xemacs-20/configure '--extra-verbose' '--with-gcc' '--cflags=-pipe -g -fomit-frame-pointer -D_GNU_SOURCE -O2 -fno-strength-reduce' '--site-includes=/usr/local/include' '--site-libraries=/usr/local/lib' '--error-checking=none' '--with-site-lisp' '--gung-ho' '--debug' '--with-offix' '--with-menubars=lucid' '--with-dialogs=athena3d' '--with-database=berkdb' '--with-ncurses' '--with-gpm' '--with-gnu-make' '--prefix=/usr/local/share/xemacs' '--with-xpm' '--with-gif' '--with-tiff' '--with-jpeg' '--with-clash-detection' '--with-session' '--package-path=/usr/local/share/xemacs/packages:~/.xemacs' '--with-mule' XEmacs 21.0-b37 "Pygmy-pre2" configured for `i486-pc-linux'. Where should the build process find the source code? /usr/src/CVS/xemacs-20 What installation prefix should install use? /usr/local/share/xemacs 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 -pipe -g -fomit-frame-pointer -D_GNU_SOURCE -O2 -fno-strength-reduce 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 Additional header files: /usr/local/include Additional libraries: /usr/local/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. 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 OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena-3d dialog boxes. Compiling in DLL support. Clash detection will use "${statedir}/xemacs/lock" for locking files. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. GCC: Reading specs from /usr/lib/gcc-lib/i486-pc-linux-gnu/egcs-2.91.24/specs gcc version egcs-2.91.24 19980418 (gcc2 ss-980401 experimental) OS: Linux genera 2.1.95 #2 Sat Apr 11 10:14:58 PDT 1998 i486 unknown LIBC: /lib/libc-2.0.92.so

1 participants
0 comments

[Failure] 21.0 "Pygmy" XEmacs Lucid (beta37) on mips-sgi-irix6.2 26 years, 2 months

Christian Nybø

My system is an sgi r5000 indy. I did cvs update; make clean, and then configure as follows: make gave this error: Thanks in advance for any help. -- chr

1 participants
0 comments

[PATCH] Frame crash and extra minibuffers fixes 26 years, 2 months

Kirill M. Katsnelson

This fixes [very probable cause for] crashes seen by Karl and Greg, and solves extra minibuffers problem in ediff, reported by Greg. The first fix fixes an error: I can crash XEmacs with my carefully crafted lisp snippet (tm). I bet a dollar that this is the cause for reported crashes. Kirill 1998-04-24 Kirill M. Katsnelson <kkm(a)kis.ru> * frame.c (Fmake_frame): GC-protect new frame immediately upon creation. 1998-04-27 Kirill M. Katsnelson <kkm(a)kis.ru> * frame.c (delete_frame_internal): Fixed spurious minibuffer frames when creating minibufferless frames (reverted to 20.3 source, change not in ChangeLog) Index: src/frame.c =================================================================== RCS file: /var/cvsroot/ntxemacs/src/frame.c,v retrieving revision 1.4 diff --unified=2 -r1.4 frame.c --- src/frame.c 1998/04/05 13:16:54 1.4 +++ src/frame.c 1998/04/26 17:33:53 ＠＠ -417,4 +417,5 ＠＠ f = allocate_frame_core (device); + XSETFRAME (frame, f); specbind (Qframe_being_created, name); ＠＠ -446,5 +447,4 ＠＠ signal_simple_error ("Invalid value for `minibuffer'", minibuf); - XSETFRAME (frame, f); update_frame_window_mirror (f); ＠＠ -1512,5 +1512,5 ＠＠ double_break_1: - if (!called_from_delete_device) + if (called_from_delete_device < 0) /* then we're being called from delete-console, and we shouldn't try to find another default-minibuffer frame for the console.

1 participants
0 comments

[PATCH]: list refs in etc/BETA 26 years, 2 months

Jason R Mastaler

1998-04-26 Jason R Mastaler <jason(a)4b.org> * etc/BETA: Replaced SmartList references in favor of Majordomo. --- etc/BETA.orig Fri Apr 3 00:09:54 1998 +++ etc/BETA Sun Apr 26 13:16:57 1998 ＠＠ -14,21 +14,21 ＠＠ --------------- If you are not subscribed to the XEmacs beta list you should be. Send -an email message with a subject of `subscribe' (without the quotes) to -xemacs-beta-request(a)xemacs.org and follow the directions. You do not -have to fill out the survey if you don't want to. +an email message to xemacs-beta-request(a)xemacs.org with `subscribe' +(without the quotes) as the BODY of the message. *** Unsubscribing ----------------- -To unsubscribe from the list send an email message with a subject of -`unsubscribe' (without the quotes) to xemacs-beta-request(a)xemacs.org. +To unsubscribe from the list send an email message to +xemacs-beta-request(a)xemacs.org with `unsubscribe' (without the quotes) +as the BODY of the message. *** Administrivia ----------------- -The XEmacs beta list is managed by the SmartList mailing list package, -and the usual SmartList commands work. Do not send mailing list +The XEmacs beta list is managed by the Majordomo mailing list package, +and the usual Majordomo commands work. Do not send mailing list requests to the main address (xemacs-beta(a)xemacs.org), always send them to xemacs-beta-request(a)xemacs.org. If you have problems with the list itself, they should be brought to the attention of the XEmacs

1 participants
0 comments

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

Adrian Aichner

>>>>> "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. Good Luck, Adrian -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Straße 2 Fax +49/89/41861-217 D-81673 MÜNCHEN E-mail aichner(a)ecf.teradyne.com

1 participants
0 comments

[SUCCESS] 21.0 "Pygmy" XEmacs Lucid (beta37) on i386-pc-solaris2.5.1 26 years, 2 months

Jason R. Mastaler

Patched up from "Philippine", built without incident. As reported in the last three betas, the Tools menu & Toolbar is still broken, but otherwise things seem fine. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/SourceTrees/xemacs-21.0-b37/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

stupid question... 26 years, 2 months

Jens Lautenbacher

Sorry if this is a faq or plain stupid, but I simply seem to be unable to get an xemacs-21 beta working... After a long time I want to again work a bit with xemacs, and so I decided to get a new package enabled xemacs-21. I downloadded the cvs xemacs-20 and xemacs-packages. But what now? I first compiled xemacs and installed, then went on tho the packages and also compiled these... but where am I supposed to install them? Do I simply link the whole structure under (prefix)/lib/xemacs/packages? That's the default path for packes if I read the docs right... But do I have to redump XEmacs? How will it know about the packages? Are they simply searched along a path on startup? WHat if there's anything that has to be dumped along with the base? After all, my XEmacs comes up with just a minimal loadpath of blabla/lisp and blabla/term. And of course nothing else is found. DO I need some initialization from lisp? WHAT TO DO and in which order? Any help would be very appreciated. PS: and sorry for any stupid faqs... BUt I'm just getting back on board and feel a bit like being washed away by the big wave just before reaching the cabin... jtl

1 participants
0 comments

[Success] 21.0 "Pygmy" XEmacs Lucid (beta37) on i586-pc-linux 26 years, 2 months

John Mignault

Patched from b36. No problems in the build. No probs so far. J > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/src/xemacs-20.5-b33/Installation: > (Output from most recent run of ./configure) uname -a: Linux jbm.dialup.access.net 2.0.31 #1 Sun Nov 9 21:45:23 EST 1997 i586 unknown ./configure '--dynamic' '--with-database=gnudbm' '--with-xpm' '--gung-ho' '--error-checking=none' XEmacs 21.0-b37 "Pygmy" configured for `i586-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-20.5-b33 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 -O2 -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 X-Face message headers. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in native sound support. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for OffiX. 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. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. > /usr/local/src/xemacs-20.5-b33/beta.err does not exist! -- #!/usr/bin/perl $dot="\x2e";$lt="\x3c";$gt="\x3e";$at="\x40"; print "J Mignault ${lt}mignault${at}nytimes${dot}com${gt}\n";

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