December 2000 - 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: Commenting out code in lisp 7 years, 2 months

Adrian Aichner

>>>>> "Paul" == Paul Krause <paulkrause1(a)mediaone.net> writes: Paul> Adrian Aichner <adrian(a)xemacs.org> writes: >> >> Do we want to make C-u M-x comment-region smarter? >> Paul> No! Make indentation smarter. If a comment begins in column Paul> 1, don't Paul> indent it when reindenting a region. This solves the Paul> problem without Paul> style-changes or hacks to comment-region. >> Paul> Have I overlooked anything? >> >> This, maybe? >> >> (Info-goto-node "(xemacs)Comments") >> >> Adrian Paul> Could you be a little more specific? I don't what you're Paul> referring to. Maybe this? Paul> You can also use `Meta-;' to align an existing comment. If a line Paul> already contains the string that starts comments, `M-;' just moves Paul> point after it and re-indents it to the conventional place. Paul> Exception: Paul> comments starting in column 0 are not moved. Yes, that, and also the following paragraph. Some major modes have special rules for indenting certain kinds of comments in certain contexts. For example, in Lisp code, comments which start with two semicolons are indented as if they were lines of code, instead of at the comment column. Comments which start with three semicolons are supposed to start at the left margin. Emacs understands these conventions by indenting a double-semicolon comment using TAB and by not changing the indentation of a triple-semicolon comment at all. You have a valid point, though. single-; comments srarting in column 0 should not be moved and comment-region would work as advertised! You opened my eyes! To All: Isn't this what we should do? Martin? Stephen? Best regards, Adrian Paul> The trouble is, it doesn't work as documented. Here's a sample. Paul> ;;; header comment Paul> ;; This function is just an example. Paul> ;;; Here either two or three semicolons are appropriate. Paul> (defun foo (x) Paul> ;;; And now, the first part of the function: Paul> (lambda (foo bar) Paul> (if (foo bar) Paul> 'bif Paul> 'baz)) Paul> ;; The following line adds one. Paul> (1+ x)) ; This line adds one. Paul> ;; This function is just an example. Paul> ;;; Here either two or three semicolons are appropriate. Paul> (defun foo (x) Paul> ;;; And now, the first part of the function: Paul> ;; The following sexp is commented out using comment-region. Paul> ; (lambda (foo bar) Paul> ; (if (foo bar) Paul> ; 'bif Paul> ; 'baz)) Paul> ;; The following line adds one. Paul> (1+ x)) ; This line adds one. Paul> I get the same indentation using either M-; or C-M-q. Paul> Testing using xemacs -vanilla on Paul> XEmacs 21.2 (beta37) "Pan" (win32) of Sun Dec 03 2000 on PAULKRAUSE Paul> as well as Paul> XEmacs 21.0 "20 minutes to Nikko" (win32) of Fri Mar 26 1999 on Paul> BLACKBIRD Paul> (which I just happen to have lying around) -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

4 participants
3 comments

Re: gud.el broken or is it just me? 23 years, 6 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

[crash] delete a buffer shown in both X and tty frames 23 years, 8 months

Yoshiaki Kasahara

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.2 (beta38) "Peisino,Ak(B" [Lucid] (i386-unknown-freebsd4.2, Mule) of Wed Dec 13 2000 on elvenbow.nc.kyushu-u.ac.jp configured using `configure --with-mule --without-xim --error-checking=all --debug --with-xfs --with-widgets=athena --without-canna --site-prefixes=/usr/local '--cflags=-g -O3 -pipe -Wall -Wno-switch -Wpointer-arith -Winline -Wmissing-prototypes -Wshadow'' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: xemacs -vanilla M-x make-frame-on-tty C-x b test (in the X frame) C-x b test (in the tty frame) C-x k (in the X frame) ** crash ** It is repeatable. It won't crash when doing C-x k in the tty frame. Lisp backtrace follows: # (condition-case ... . error) # (catch top-level ...) C backtrace follows: (gdb) where #0 0x286323e0 in kill () from /usr/lib/libc.so.4 #1 0x80bb823 in fatal_error_signal (sig=6) at emacs.c:535 #2 0xbfbfffac in ?? () #3 0x80be869 in assert_failed (file=0x824d9a7 "eval.c", line=1885, expr=0x824d508 "abort()") at emacs.c:3214 #4 0x80c12f1 in signal_1 (sig=137300068, data=142340244) at eval.c:1885 #5 0x80c2791 in error (fmt=0x8285dc0 "Marker does not point anywhere") at eval.c:2052 #6 0x8194e66 in marker_position (marker=141246172) at marker.c:354 #7 0x81afc17 in redisplay_window (window=141753344, skip_selected=0) at redisplay.c:5896 #8 0x81b098c in redisplay_frame (f=0x8738400, preemption_check=0) at redisplay.c:6393 #9 0x81b0b6f in redisplay_device (d=0x870a600, automatic=1) at redisplay.c:6467 #10 0x81b0edd in redisplay_without_hooks () at redisplay.c:6556 #11 0x81b8ee6 in redisplay () at redisplay.c:6613 #12 0x8114eca in Fnext_event (event=141418308, prompt=137299972) at event-stream.c:2176 #13 0x80a2ce9 in Fcommand_loop_1 () at cmdloop.c:574 #14 0x80a2f96 in command_loop_1 (dummy=137299972) at cmdloop.c:494 #15 0x80cac25 in condition_case_1 (handlers=137300068, bfun=0x80a2f58 <command_loop_1>, barg=137299972, hfun=0x80a3008 <cmd_error>, harg=137299972) at eval.c:1651 #16 0x80a30f7 in command_loop_2 (dummy=137299972) at cmdloop.c:256 #17 0x80cab24 in internal_catch (tag=137384396, func=0x80a30bc <command_loop_2>, arg=137299972, threw=0x0) at eval.c:1317 #18 0x80a256e in initial_command_loop (load_me=137299972) at cmdloop.c:305 #19 0x80bcb9f in xemacs_21_2_b38_i386_unknown_freebsd4_2 (argc=2, argv=0xbfbff5b4, envp=0xbfbff5c0, restart=0) at emacs.c:2253 #20 0x80bead1 in main (argc=2, argv=0xbfbff5b4, envp=0xbfbff5c0) at emacs.c:2682 #21 0x80808e9 in _start () -- Yoshiaki Kasahara Computing and Communications Center, Kyushu University kasahara(a)nc.kyushu-u.ac.jp

3 participants
12 comments

RoboCup 23 years, 9 months

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

Custom "done" button takes away the current buffer 23 years, 9 months

Konstantin Malakhanov

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.2 (beta34) "Molpe" [Lucid] (i586-pc-win32) of Fri Jun 09 2000 on NEVERYON configured using `configure UNKNOWN' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: The "done" button in any customization buffer takes away the current buffer, not the customization buffer itself. It is very annoing, if you are sitting in another buffer and press "done" in the customization buffer - the buffer you were in will be gone! (buried or killed) -- Konstantin Malakhanov ISOWARE GmbH, Feithstr. 142, 58097 Hagen, Germany email: km(a)isoware.de Tel: 02331/8019-67 FAX: 02331/8019-99

3 participants
2 comments

buffers-tab face not updated properly 23 years, 9 months

John A. Turner

I've been playing around with the buffers-tab face - currently it's: '(buffers-tab ((t (:foreground "firebrick4" :background "gray60" :size "10" :family "helvetica" :italic t))) t) most of the time all the tab labels show up as firebrick4, but sometimes some of the tabs show up as black rather than firebrick4, as shown below -- John A. Turner, Senior Research Associate Blue Sky Studios, One South Rd, Harrison, NY 10528 http://www.blueskystudios.com/ (914) 825-8319

3 participants
6 comments

Re: outstanding issues, "dired" in the Subject header 23 years, 10 months

Michael Sperber

>>>>> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: >>>>> "Michael" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes: APA> Hello Michael, APA> could you please consider APA> http://www.xemacs.org/list-archives/xemacs-patches/199908/msg00033.html APA> for inclusion into your upcoming dired release? No problem; it's long been applied to my workspace. APA> I am willing to test the new version before release. For now, I'd be grateful for some EFS testers (for the version currently in CVS). -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

2 participants
1 comments

external widget: events lost 23 years, 10 months

Ilya N. Golubev

Keyboard events from external client window do not reach xemacs (XtAppProcessEvent inside xemacs does not return). Mouse events are OK (XtAppProcessEvent returns and all keyboard input handled properly). When I use Xt external client, keyboard events are always lost. When I use Xm external client, initially this also happens, but after some mouse actions in client window it inpredictably becomes OK. Client program is always the same, it is just linked with different libextcli. X environment: x11 5, motif 1.2 (SCO xds 5.2.5h, SCO BaseX 5.1.1b) `Installation': uname -a: SCO_SV d-fens 3.2 2 i386 ../xemacs-21.1/configure '--compiler=gcc-2.95.2' '--prefix=/usr' '--debug' '--error-checking=all' '--external-widget' '--with-socks' '--verbose' XEmacs 21.1.12 "Channel Islands" configured for `i586-unknown-sco3.2v5.0.2'. Where should the build process find the source code? /home/gin/xemacs-21.1 What installation prefix should install use? /usr What operating system and machine description files should XEmacs use? `s/sco5.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc-2.95.2 -g -O99 -mpentium -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? Where do we find X Windows libraries? /usr/lib Compiling in support for SOCKS. 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 support for DBM. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" 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
5 comments

recent VM vs gutter patches ???? 23 years, 10 months

Giacomo Boffi

i built yesterday, against the latest CVS, and apparently everything continued to be OK, except for VM i use a pixmap for my bg, but now VM randomly modifies the bg of its windows and also the bg of the minibuffer (sometimes it's my pixmap, sometimes it's the default background color that i set in .Xdefaults) ciao

4 participants
13 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 2000