December 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Ben Wing

I've compiled a short list of bugs that I consider to be showstoppers for the 21.0 release. It's located at: http://devel.xemacs.org/xemacs/showstoppers.html Ben (typed by Martin)

6 participants
6 comments

Re: gud.el broken or is it just me? 23 years, 9 months

SL Baur

Aki Vehtari <Aki.Vehtari(a)hut.fi> writes in xemacs-beta(a)xemacs.org: ... > Btw. gud.el in XEmacs is dated 1993 and gud.el in emacs-20.3 is > dated 1998. Unfortunately gud.el in emacs-20.3 does not work in > XEmacs and I don't know much work it would need to make it work and I've done the initial port of gud.el to XEmacs. It mostly works[1], but it sorely lacks the functionality in gdbsrc.el. Making a gudsrc.el mode is on my list of things to do. It was in ftp://altair.xemacs.org/pub/xemacs-futures/ when I was on the 'net. It was delayed integration into the XEmacs packages pending 21.0 release. I also have a ported cua-mode.el to integrate. NOTE: The gud.el and cua-mode.el XEmacs portings are courtesy of Altrasoft, Inc. Thank you Altrasoft. Footnotes: [1] I have a report that my port does not work on Solaris with dbx.

2 participants
1 comments

RoboCup 24 years

Akram Khodadadi

Hello Please answer my question. We maked a player in Linux with Lisp languaege ,but we dont know how to make a UDP connection between our player and the server with Lisp languaege. We looked in many sources ,but we didn't attain any affects. Please say to us for making a UDP connection and geting and sending messages with that Lisp languaege which orders . Please explan with an example. Thanks Mrs Khodadadi

3 participants
2 comments

XEmacs 21.0.60 core dumps on FreeBSD 2.2.6 26 years, 1 month

Richard Coleman

After getting a core dump with 21.2.8, I thought I would try 21.0.60 and see if I had better luck. I also get a core dump with this version. I don't think it's my machine, since I just built 20.4 as well, and it works fine. I've attached a lisp backtrace, a gdb backtrace, and the Installation file. -- Richard Coleman coleman(a)math.gatech.edu Fatal error: assertion failed, file window.h, line 245, RECORD_TYPEP (_obj, lrecord_window) || MARKED_RECORD_P (_obj) Fatal error (6). Your files have been auto-saved. Use `M-x recover-session' to recover them. Please report this bug by running the send-pr script included with XEmacs, or selecting `Send Bug Report' from the help menu. As a last resort send ordinary email to `crashes(a)xemacs.org'. *MAKE SURE* to include the information in the command M-x describe-installation. If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started the editor, or maybe in your home directory), and type gdb /home/rcoleman/xemacs/xemacs-21.0.60/src/xemacs core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: redisplay-echo-area() # bind (inhibit-read-only zmacs-region-stays stdout-p frame message) raw-append-message("Error in init file: Symbol's function definition is void: display-time" #<x-frame "emacs" 0x8fd> nil) # bind (stdout-p frame message label) append-message(message "Error in init file: Symbol's function definition is void: display-time" nil nil) # bind (stdout-p frame message label) display-message(message "Error in init file: Symbol's function definition is void: display-time") # bind (str args fmt) message("Error in init file: %s" "Symbol's function definition is void: display-time") byte-code("..." [message "Error in init file: %s" error-message-string error display-warning initialization format "An error has occurred while loading %s:\n\n%s\n\nTo ensure normal operation, you should investigate the cause of the error\nin your initialization file and remove it. Use the `-debug-init' option\nto XEmacs to view a complete error backtrace." user-init-file t init-file-had-error] 7) # bind (error debug-on-error debug-on-error-from-init-file debug-on-error-should-be-set debug-on-error-initial) load-init-file() # bind (command-line-args-left) command-line() # (unwind-protect ...) normal-top-level() # (condition-case ... . error) # (catch top-level ...) (gdb) bt #0 0x203e7b61 in ?? () #1 0x44743 in fatal_error_signal (sig=6) at emacs.c:262 #2 0xefbfdfdc in ?? () #3 0x46f5b in assert_failed (file=0x11a87c "window.h", line=245, expr=0x11a83e "RECORD_TYPEP (_obj, lrecord_window) || MARKED_RECORD_P (_obj)") at emacs.c:2608 #4 0x12d696 in Fredisplay_echo_area () at window.h:245 #5 0x4d50a in funcall_recording_as (recorded_as=-1607563140, nargs=0, args=0xefbfc3bc) at eval.c:3197 #6 0x4d785 in Ffuncall (nargs=1, args=0xefbfc3bc) at eval.c:3238 #7 0x198a6 in Fbyte_code (bytestr=1612954684, vector=-2145141644, maxdepth=5) at bytecode.c:416 #8 0x4e6f3 in funcall_lambda (fun=539213024, nargs=3, arg_vector=0xefbfc584) at eval.c:3597 #9 0x4d691 in funcall_recording_as (recorded_as=-1607016668, nargs=3, args=0xefbfc580) at eval.c:3214 #10 0x4d785 in Ffuncall (nargs=4, args=0xefbfc580) at eval.c:3238 #11 0x198a6 in Fbyte_code (bytestr=1612954536, vector=-2145141796, maxdepth=4) at bytecode.c:416 #12 0x4e6f3 in funcall_lambda (fun=539212800, nargs=4, arg_vector=0xefbfc6e8) at eval.c:3597 #13 0x4d691 in funcall_recording_as (recorded_as=-1607565844, nargs=4, args=0xefbfc6e4) at eval.c:3214 #14 0x4d785 in Ffuncall (nargs=5, args=0xefbfc6e4) at eval.c:3238 #15 0x198a6 in Fbyte_code (bytestr=1612954916, vector=-2145141440, maxdepth=5) at bytecode.c:416 #16 0x4e6f3 in funcall_lambda (fun=539213152, nargs=2, arg_vector=0xefbfc888) at eval.c:3597 #17 0x4d691 in funcall_recording_as (recorded_as=-1607565796, nargs=2, args=0xefbfc884) at eval.c:3214 #18 0x4d785 in Ffuncall (nargs=3, args=0xefbfc884) at eval.c:3238 #19 0x198a6 in Fbyte_code (bytestr=1612955216, vector=-2145141124, maxdepth=4) at bytecode.c:416 #20 0x4e6f3 in funcall_lambda (fun=539213476, nargs=2, arg_vector=0xefbfca14) at eval.c:3597 #21 0x4d691 in funcall_recording_as (recorded_as=-1607572396, nargs=2, args=0xefbfca10) at eval.c:3214 #22 0x4d785 in Ffuncall (nargs=3, args=0xefbfca10) at eval.c:3238 #23 0x198a6 in Fbyte_code (bytestr=1613020268, vector=-2145076068, maxdepth=7) at bytecode.c:416 #24 0x4ce3c in Feval (form=1076149340) at eval.c:3063 #25 0x4a6e3 in run_condition_case_handlers (val=1078148508, var=-1607671708) at eval.c:758 #26 0x4a846 in condition_case_3 (bodyform=1076149240, var=-1607671708, handlers=1076149316) at eval.c:1636 #27 0x19c73 in Fbyte_code (bytestr=1613019924, vector=-2145076340, maxdepth=4) at bytecode.c:576 #28 0x4e6f3 in funcall_lambda (fun=539278836, nargs=0, arg_vector=0xefbfd09c) at eval.c:3597 #29 0x4d691 in funcall_recording_as (recorded_as=-1607060348, nargs=0, args=0xefbfd098) at eval.c:3214 #30 0x4d785 in Ffuncall (nargs=1, args=0xefbfd098) at eval.c:3238 #31 0x198a6 in Fbyte_code (bytestr=1613018836, vector=-2145077436, maxdepth=4) at bytecode.c:416 #32 0x4e6f3 in funcall_lambda (fun=539277320, nargs=0, arg_vector=0xefbfd460) at eval.c:3597 #33 0x4d691 in funcall_recording_as (recorded_as=-1607060516, nargs=0, args=0xefbfd45c) at eval.c:3214 #34 0x4d785 in Ffuncall (nargs=1, args=0xefbfd45c) at eval.c:3238 #35 0x198a6 in Fbyte_code (bytestr=1613016916, vector=-2145079288, maxdepth=6) at bytecode.c:416 #36 0x4e6f3 in funcall_lambda (fun=539275724, nargs=0, arg_vector=0xefbfd518) at eval.c:3597 #37 0x4df72 in apply_lambda (fun=539275724, numargs=0, unevalled_args=-1607671804) at eval.c:3501 #38 0x4cfeb in Feval (form=1076952004) at eval.c:3085 #39 0x4a568 in condition_case_1 (handlers=-1607671708, bfun=0x4c434 <Feval>, barg=1076952004, hfun=0x23754 <cmd_error>, harg=-1607671804) at eval.c:1653 #40 0x2493d in top_level_1 (dummy=-1607671804) at cmdloop.c:206 #41 0x4a388 in internal_catch (tag=-1607594132, func=0x24914 <top_level_1>, arg=-1607671804, threw=0x0) at eval.c:1328 #42 0x23901 in initial_command_loop (load_me=-1607671804) at cmdloop.c:285 #43 0x45969 in xemacs_21_0_b60_i386_unknown_freebsd2_2_6 (argc=1, argv=0xefbfd80c, envp=0xefbfd814, restart=0) at emacs.c:1705 #44 0x46322 in main (argc=1, argv=0xefbfd80c, envp=0xefbfd814) at emacs.c:2122 uname -a: FreeBSD phaedrus.cmb.net 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: Wed Mar 25 02:28:49 GMT 1998 jkh＠time.cdrom.com:/usr/src/sys/compile/GENERIC i386 ./configure '--prefix=/home/rcoleman/beta' '--site-includes=/usr/local/include' '--site-libraries=/usr/local/lib' XEmacs 21.0-b60 "Poitou60" configured for `i386-unknown-freebsd2.2.6'. Where should the build process find the source code? /home/rcoleman/xemacs/xemacs-21.0.60 What installation prefix should install use? /home/rcoleman/beta What operating system and machine description files should XEmacs use? `s/freebsd.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 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 Additional header files: /usr/local/include Additional libraries: /usr/local/lib Runtime library search path: /usr/local/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 proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "flock" for locking mail spool files. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. 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: ---------------------------------------------------------

3 participants
3 comments

temporary-file-directory 26 years, 2 months

Lars Magne Ingebrigtsen

Emacs has temporary-file-directory, which defaults to "/tmp/". It's a nice variable to have, since all other temp dir variables can use that variable as the default value, so I think XEmacs should have it as well. -- (domestic pets only, the antidote for overdose, milk.) larsi(a)ifi.uio.no * Lars Magne Ingebrigtsen

5 participants
4 comments

Re: XEmacs 21 /vs./ my keyboard: I want my DEL back 26 years, 2 months

Karl Kleinpaste

Glynn Clements <glynn(a)sensei.co.uk> writes: > XEmacs treats the code which corresponds to the VERASE character as > Backspace (i.e. it is consistent with the kernel's tty driver). If > your Backspace key generates \010, then you need to use > stty erase ^V^H > to tell the tty driver about it. No. [1007] [22:30:27] beaver:~> stty -a speed 38400 baud; rows 67; columns 80; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^G; eof = ^D; eol = <undef>; ^^ I hit the key that generates \177 in an xterm, and XEmacs 21 calls it a "BS". This is wrong. The fundamental problem is that, within a terminal, the set of 3 distinct concepts "Delete", "Backspace", and "`C-h'" do not all exist, the 2nd & 3rd being the same thing. XEmacs 21 has mis-commandeered the first, which arrives as \177, misinterpreting it as "BS", which doesn't even exist in a terminal. This breaks many standard and common keymaps, Gnus' keymaps just being particularly good examples of a large, complex system's keymaps which have lots of references to multi-key sequences including <delete> but which have no knowledge of this peculiar thing called "BS". (Just to expand on the example, Gnus' *Group* buffer believes in "G delete" and "T delete", neither of which works in an xterm due to this problem.) 20.4 shares none of this braindamage, which understands "delete" in all contexts. 20.4 tells me that "delete runs the command backward-or-forward-delete-char" and "B delete runs the command gnus-summary-delete-article" when run both under X directly and within an xterm.

2 participants
1 comments

Re: `The Bazaar' conference in new york? 26 years, 2 months

WJCarpenter

matt> That and network TV stations that actually turn off at night. I matt> fear, however, that I may have just dated myself. =) Oh, I don't know about that. Happens even in some big cities. For example, I was once Beijing watching an English language movie** in my hotel room. The TV station went off the air at 11pm, right in the middle of the movie. I'm guessing that Beijing is larger than West Lafayette, Indiana. [**] Apparently, they show English language programming as a language practice exercise. Huge portions of the populous are trying to learn English, but they have for practice mostly other Chinese who are also trying to learn English. So, the the People In Charge, actually watching the movie for entertainment value is a secondary or tertiary consideration. -- bill(a)carpenter.ORG (WJCarpenter) PGP bill(a)bubblegum.net 0x91865119 38 95 1B 69 C9 C6 3D 25 73 46 32 04 69 D6 ED F3

1 participants
0 comments

Re: 21.2.6 death under mule and mswindows 26 years, 2 months

Didier Verna

[ Martin, please discard my last mail for now ] Martin Buchholz writes: dv> For me under Solaris, Mule/X11 works well until 21.2.6 (included). >>> From then, it's unusable (it crashes at the first X frame initialization). dv> Unfortunately, I don't have time to debug this crash. Martin> This is rather surprising to me - one would have thought that 21.2.6 Martin> was infinitely more broken than 21.2.7. Andy's subwindow support looks Martin> like the most likely suspect - maybe it should have been delayed one Martin> beta. Didier's crash is noooooo crash, I repeat NO CRASH ... I finally got 1 hour or two to deal with this problem this afternoon. After a while, I found a place where the dumped lisp code from startup.el was finding a bogus number of arguments to pass to make-frame. This sounded like a bytecode bug, so out of curiosity, I just removed all dumped elcs and re-byte-compiled them. Guess what ... the crash is gone. I still don't really understand how this can have happened. There was not supposed to be any change in the bytecode lately right ? BTW: it seems that from severals 21.2 betas, my old crash preventing me from opening a frame on another display is gone too. Woao, '98 ends up in a real festival !! Happy new year ! -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

option->font menu does not work 26 years, 2 months

Ralf Weidemann

I mean that the font menu did already work in an earlier 21.0 beta (<60), but now it does not work either in Artemis or Poitou. Ralf XEmacs 21.2 "Artemis" [Lucid] (powerpc-unknown-linux) of Thu Dec 31 1998 on onyx Button descriptor has an odd number of keywords and values: [["Fixed" ("Bold" "Medium") (0 50 60 70 80 90 100 110 120 130 140 150 170 200 230) nil] "Fixed" 120 "Medium" "R"] Getting list of fonts from server... done. Getting list of fonts from server... Loading x-font-menu...done Loading x-font-menu... XEmacs 21.0 "Poitou" [Lucid] (powerpc-unknown-linux) of Sun Dec 13 1998 on onyx nil may not appear in menu descriptions nil may not appear in menu descriptions Getting list of fonts from server... done. Getting list of fonts from server... Loading x-font-menu...done Loading x-font-menu...

1 participants
0 comments

Re: W3 Broken in 21.2 26 years, 2 months

John Mignault

>>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: Martin> My fault: Try this patch: <patch snipped> Thanks, that seems to have solved the problem. j Martin> Because this is so important and small, I'll commit it to Martin> CVS right away. Martin> Martin -- #!/usr/bin/perl $dot="\x2e";$lt="\x3c";$gt="\x3e";$at="\x40"; print "J Mignault ${lt}jbm${at}panix${dot}com${gt}\n"; $wright = qq(When a man talks dirty to a woman, it's sexual harassment. When a woman talks dirty to a man, it's $3.95 per minute.);

1 participants
0 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 December 1998