November 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Is it ok to call CONSOLE_HAS_METHOD() after initialization? 25 years

William M. Perry

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > wmperry(a)aventail.com (William M. Perry) writes: > > > Nope, that's not how it works - you tell it what method and it > > automatically constructs the function name from the console type (tty) and > > method name (set_mouse_position). I just cheat a little and set the method > > slots directly. > > Ah you're right of course. Maybe you should just introduce that macro > (or change the function to do nothing, that might be cleaner). Well, the console code already has a 'dummy' method it uses. I want to avoid duplicating it if I can, just so the two do not get out of synch. This is all kind of moot right now anyway, since the Gpm_GetSnapshot appears to return useless positions (negative, etc). :( -Bill P.

1 participants
0 comments

Re: 21.2-b19 "Sneaky Bastard 19991102" crashes when using toolbar for Ediff control buffer 25 years

Jan Vroonhof

ALTMARK(a)de.ibm.com writes: > In XEmacs 21.2 (beta19) "Sneaky Bastard 19991102" [Lucid] (i686-pc-linux) of Aha.. So there are people using it. > Please describe exactly what actions triggered the bug > and the precise symptoms of the bug: I'll try to reproduce at home this weekend. -- Jan Vroonhof http://www.math.ethz.ch/~vroonhof/ Mathematik, vroonhof ＠ math.ethz.ch HG E16, ETH-Zentrum, Tel: +41-1-6325456/25154 Raemistrasse 101, CH-8092 Zuerich. Fax: +41-1-6321085

1 participants
0 comments

Re: [Yusuf Goolamabbas <yusufg@outblaze.com>] [dgaudet@arctic.org: faster malloc for multithreaded programs] 25 years

Jan Vroonhof

Marcus Thiessel <thiessel(a)bbn.hp.com> writes: > > Hoard is a fast, scalable, and memory-efficient replacement > > for malloc/free for multiprocessors. The newest release (1.2) > > incorporates a user-level lock implementation (for x86, SPARC, FWIW? XEmacs cpu usage isn't dominated by time spent in malloc is it? I don't see the point at this moment to change to another allocator if that takes more space and isn't as portable as we use now. Jan

1 participants
0 comments

Re: Is it ok to call CONSOLE_HAS_METHOD() after initialization? 25 years

Jan Vroonhof

wmperry(a)aventail.com (William M. Perry) writes: > Nope, that's not how it works - you tell it what method and it > automatically constructs the function name from the console type (tty) and > method name (set_mouse_position). I just cheat a little and set the method > slots directly. Ah you're right of course. Maybe you should just introduce that macro (or change the function to do nothing, that might be cleaner). Jan

1 participants
0 comments

21.2-b19 "Sneaky Bastard 19991102" crashes when using toolbar for Ediff control buffer 25 years

ALTMARK＠de.ibm.com

--text follows this line-- 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 (beta19) "Sneaky Bastard 19991102" [Lucid] (i686-pc-linux) of Thu Nov 4 1999 on altmark configured using `configure --site-includes=/usr/local/include --site-libraries=/usr/local/lib --cflags=-O3 --debug=no --error-checking=none --prefix /usr/local/test/xemacs' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: Actions: 1. Started Xemacs: /usr/local/test/xemacs/bin/xemacs -vanilla & 2. Chose to use a toolbar with Ediff control buffer: Tools -> Ediff Miscellanea -> Use a toolbar with Ediff control buffer 3. Compared two files with Ediff (e.g. ~/.xemacs/lisp/.emacs and ~/.xemacs/lisp/.emacs~): Tools -> Compare -> Two Files... 4. After the Ediff session came up, moved the mouse pointer to the Ediff control buffer. Jumped between some diffs using the corresponding toolbar button and also the keys <SPC> and <p>. 5. Moved the mouse pointer out of the Ediff control buffer. Crash ... Notes: 1. This doesn't happen when no toolbar for the Ediff control buffer is used. 2. This doesn't happen with 21.2-b19 built from the latest available tarballs. (Compiled with the same options.) 3. Same crash with built for AIX 4.3.2 (also in line 7517 of redisplay.c). Screen messages (on xterm from which XEmacs was started): root＠altmark: /root (2) # Fatal error: assertion failed, file redisplay.c, line 7517, abort() 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 /usr/local/test/xemacs/bin/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: event-window(#<motion-event 86, 4>) # bind (frame event) default-mouse-motion-handler(#<motion-event 86, 4>) # (condition-case ... . error) # (catch top-level ...) [1]+ Aborted (core dumped) /usr/local/test/xemacs/bin/xemacs -vanilla C stack backtrace: (gdb) where #0 0x40303ab1 in __kill () from /lib/libc.so.6 #1 0x807d019 in fatal_error_signal () #2 0x403039b8 in __restore () at ../sysdeps/unix/sysv/linux/i386/sigaction.c:125 #3 0x40304ef3 in abort () at ../sysdeps/generic/abort.c:88 #4 0x807cf7e in assert_failed () #5 0x8112604 in start_end_of_last_line () #6 0x8114f69 in pixel_to_glyph_translation () #7 0x8088763 in event_pixel_translation () #8 0x8089d45 in Fevent_window () #9 0x8080c25 in Ffuncall () #10 0x805c33a in execute_optimized_program () #11 0x805bf56 in funcall_compiled_function () #12 0x8080de2 in Ffuncall () #13 0x8084060 in call1 () #14 0x80a5d78 in execute_internal_event () #15 0x80a8316 in Fdispatch_event () #16 0x8064bcf in Fcommand_loop_1 () #17 0x8064e16 in command_loop_1 () #18 0x8084beb in condition_case_1 () #19 0x8064f0c in command_loop_2 () #20 0x8084ab9 in internal_catch () #21 0x80648e0 in initial_command_loop () #22 0x807b96b in xemacs_21_2_b19_i686_pc_linux () #23 0x807d27d in main () #24 0x402fd213 in __libc_start_main (main=0x807d160 <main>, argc=2, argv=0xbffff844, init=0x804dc50 <_init>, fini=0x817baa0 <_fini>, rtld_fini=0x4000ac30 <_dl_fini>, stack_end=0xbffff83c) at ../sysdeps/generic/libc-start.c:90 Output of `M-x describe-installation': uname -a: Linux altmark 2.2.10 #1 Tue Jul 20 16:32:24 MEST 1999 i686 unknown ./configure '--site-includes=/usr/local/include' '--site-libraries=/usr/local/lib' '--cflags=-O3' '--debug=no' '--error-checking=none' '--prefix' '/usr/local/test/xemacs' XEmacs 21.2-b19 "Sneaky Bastard 19991102" configured for `i686-pc-linux'. Where should the build process find the source code? /build/xemacs/xemacs-cvs-snapshot-19991102 What installation prefix should install use? /usr/local/test/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 -O3 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/X11/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 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 native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for LDAP. 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-3d native widgets. Using Athena-3d dialog boxes. Compiling in DSO module support. movemail will use "dot-locking" for locking mail spool files. Recent keystrokes: misc-user Recent messages (most recent first): Loading mail-abbrevs... Loading emacsbug...done Loading emacsbug... --- Markus Alt IBM Laboratory Boeblingen, Germany

1 participants
0 comments

Re: Missing hm--html-menus package 25 years

Jan Vroonhof

john s jacobs anderson <jacobs(a)xemacs.org> writes: > Sean> So I looked into how this download mechanism works - looked up > Sean> /pub/xemacs/packages on the xemacs.org server and found that > Sean> there is no hm--html-menus package there. Then I had a look at > Sean> the packages-index.LATEST file, and found that the > Sean> hm--html-menus package is listed there. So I guess that there's > Sean> an inconsistency between the files on the server and the index > Sean> file. You are correct. The hm--html-menus is missing from the FTP site. You either need the SUMO tarball or get it from the authors site. A new release of the packages is badly needed, but requires some organisational changes that are currently being worked on. Jan

1 participants
0 comments

Re: Is it ok to call CONSOLE_HAS_METHOD() after initialization? 25 years

Jan Vroonhof

wmperry(a)aventail.com (William M. Perry) writes: > And it actually seems to work. Unfortunately there is no > CONSOLE_NO_LONGER_HAS_METHOD(...) macro to go with it. :) Just call CONSOLE_HAS_METHOD with a NULL method value? JAn

1 participants
0 comments

Re: Stupid question: How to get Backspace working in TTY mode? 25 years

Jan Vroonhof

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > kazz> You could just do "stty erase ^H", instead of using "Delete" for > kazz> erase. > kazz> You'd lose Backspace for help-command prefix but you could use f1. > > Sure, F1 works. But I don't really want to globally use ^H for > erase. Then why do you have your backspace generating that code? Note that the problem is that most shell support ^H as erase regardless of the stty setting and thus hide the problem. Try something less intelligent that takes tty input and you'll see that ^h doesn't work there too. > Why can't I rebind the damn key in XEmacs? You can. Just set tty-erase-char explicitly. However you really don't want to do that. What you really want is to make your backspace key generate DEL instead. For instance in xterms you do this XTerm*vt100.translations: #override <Key>BackSpace: string(0x7f) \n\ <Key>Delete: string(0x1b) string([3~) Every terminal emulator worthy of the name has a similar option. Jan

1 participants
0 comments

Re: Stupid question: How to get Backspace working in TTY mode? 25 years

Michael Sperber

>>>>> "Stef" == Stef Epardaud <stef(a)lunatech.com> writes: Stef> xemacs -nw -vanilla ? Stef> it does it for me without any special config. Not for me, at least not for 21.1.3 inside an XEmacs. I have this vague feeling it used to work, but I don't know when or in what version. Stef> On Wed, Nov 03, 1999 at 03:11:03PM +0100, Michael Sperber [Mr. Preprocessor] wrote: >> >> I really felt stupid when someone asked me how to make Backspace >> delete backwards in TTY mode, and I didn't know. This seems to be FAQ >> material, but isn't in the FAQ. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

2 participants
1 comments

Re: compiler warnings patch 25 years

Jan Vroonhof

Stef Epardaud <stef(a)lunatech.com> writes: > - return len + asso_values[str[2]] + asso_values[str[0]]; > + return len + asso_values[(int)str[2]] + asso_values[(int)str[0]]; > } This one is correct. > - int len; > + int len=0; > int result_len; > > /* read in "n/m:" (n=client fd, m=message length) */ This is just the compiler being stupid. If you want to fix better it much better to rewrite the read-in loop to be more clear, using a do { } while or a for loop. I didn't look at the rest yet. Jan

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 November 1999