March 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Pixel-based scrolling mystery 25 years

Jan Vroonhof

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > Now, why doesn't dragging work? I'm sure that's what most people mean > when they refer to pixel-based scrolling. Having scrollbar *buttons* > scroll pixel by pixel is pretty useless. Because the pixel based scrolling works by applying a heuristic in window_scroll. Dragging the scrollbar however calls set-window-start directly. Somebody needs to implement a similar heuristic in scrollbar-vertical-drag. Jan

1 participants
0 comments

Re: crash when using W3 25 years

Jan Vroonhof

I was looking for an example image to double check the pixel bases scrolling stuffed, and I got this crash when visiting my home page with -O3. (it is reproducible, but I have to real work now, maybe you have some more ideas. > "Manfred Bartz" <MBartz(a)xix.com> writes: > > > (gdb) where > > #3 0x813b021 in bufpos_to_bytind (buf=0x895a8b0, x=0) at insdel.c:1116 > > #4 0x80f1764 in report_extent_modification (buffer=144025776, start=0, end=0, afterp=1) at extents.c:2272 > Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > > > This supposed to be fixed.. in 21.2.27+ (I am not sure those > > parameter values are correct). > > > > Hrvoje? Hrvoje Niksic <hniksic(a)iskon.hr> writes: > > This might be a different bug from the one I fixed. This crash comes > from signal_after_change() being called with START==0, which triggers > the assert in bufpos_to_bytind. Also, the backtrace seems weird -- I > wonder if it comes from an optimized build? > [rest of discussion deleted] This is from a uname -a: Linux urysohn 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 i686 unknown ../configure '--debug=no' '--error-checking=none' '--with-athena=3d' XEmacs 21.2-b31 "Iris" configured for `i686-pc-linux'. Where should the build process find the source code? /scratch/vroonhof/xemacs 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 -O3 -Wall -Wno-switch -Wpointer-arith -Winline -Wmissing-prototypes -Wshadow (gdb) where #0 0x80a2c0d in map_extents_bytind (from=0, to=0, fn=0x80a6750 <report_extent_modification_mapper>, arg=0xbfffec0c, obj=142090312, after=0x0, flags=15360) at /scratch/vroonhof/xemacs/src/extents.c:1972 #1 0x80aadea in report_extent_modification (buffer=142090312, start=0, end=0, afterp=1) at /scratch/vroonhof/xemacs/src/extents.c:2281 #2 0x80dbd86 in signal_after_change (buf=0x8782048, start=0, orig_end=1, new_end=0) at /scratch/vroonhof/xemacs/src/insdel.c:2291 #3 0x80dc519 in buffer_insert_string_1 (buf=0x8782048, pos=1, nonreloc=0xbfffed48 "HTTP/1.1 200 OK\r\nDate: Fri, 17 Mar 2000 13:24:28 GMT\r\nServer: Apache/1.3.3 (Unix) mod_perl/1.16\r\nLast-Modified: Fri, 17 Dec 1999 14:10:50 GMT\r\nETag: \"1f26-915-385a446a\"\r\nAccept-Ranges: bytes\r\nContent-"..., reloc=136077476, offset=0, length=1024, flags=0) at /scratch/vroonhof/xemacs/src/insdel.c:2564 #4 0x80dd86f in buffer_insert_raw_string_1 (buf=0x8782048, pos=-1, nonreloc=0xbfffed48 "HTTP/1.1 200 OK\r\nDate: Fri, 17 Mar 2000 13:24:28 GMT\r\nServer: Apache/1.3.3 (Unix) mod_perl/1.16\r\nLast-Modified: Fri, 17 Dec 1999 14:10:50 GMT\r\nETag: \"1f26-915-385a446a\"\r\nAccept-Ranges: bytes\r\nContent-"..., length=1024, flags=0) at /scratch/vroonhof/xemacs/src/insdel.c:2584 #5 0x80f2cc8 in read_process_output (proc=142117904) at /scratch/vroonhof/xemacs/src/process.c:921 #6 0x809ddba in execute_internal_event (event=139809960) at /scratch/vroonhof/xemacs/src/event-stream.c:2953 #7 0x809f6f6 in Fdispatch_event (event=139809960) at /scratch/vroonhof/xemacs/src/event-stream.c:4207 #8 0x8062f7f in Fcommand_loop_1 () at /scratch/vroonhof/xemacs/src/cmdloop.c:575 #9 0x806318e in command_loop_1 (dummy=136077476) at /scratch/vroonhof/xemacs/src/cmdloop.c:490 #10 0x807f3cb in condition_case_1 (handlers=136077572, bfun=0x8063178 <command_loop_1>, barg=136077476, hfun=0x8062a90 <cmd_error>, harg=136077476) at /scratch/vroonhof/xemacs/src/eval.c:1644 #11 0x806326c in command_loop_2 (dummy=136077476) at /scratch/vroonhof/xemacs/src/cmdloop.c:252 #12 0x807f2af in internal_catch (tag=136149260, func=0x8063234 <command_loop_2>, arg=136077476, threw=0x0) at /scratch/vroonhof/xemacs/src/eval.c:1310 #13 0x8062ccc in initial_command_loop (load_me=136077476) at /scratch/vroonhof/xemacs/src/cmdloop.c:301 #14 0x8076db2 in xemacs_21_2_b31_i686_pc_linux (argc=1, argv=0xbffff494, envp=0xbffff49c, restart=0) at /scratch/vroonhof/xemacs/src/emacs.c:1872 #15 0x80786f8 in voodoo_free_hook (mem=0x1) at /scratch/vroonhof/xemacs/src/emacs.c:2291 #16 0x4031c1eb in __libc_start_main (main=0x80785f8 <main>, argc=1, argv=0xbffff494, init=0x804e260 <_init>, fini=0x8157d10 <_fini>, rtld_fini=0x4000a610 <_dl_fini>, stack_end=0xbffff48c) at ../sysdeps/generic/libc-start.c:90

1 participants
0 comments

Re: Pixel-based scrolling mystery 25 years

Jan Vroonhof

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > "Wow," says I, "we have pixel-based scrolling, and I wasn't even aware > of it." But no matter how hard I try, I cannot get it to work. > Dragging the scrollbar scrolls by lines. It works for me (but not when dragging).. Try using the buttons on your scrollbar that allow you to step line by line. Jan

1 participants
0 comments

Re: 25 years

Hrvoje Niksic

wmperry(a)aventail.com (William M. Perry) writes: > Well, other than that the current version of Emacs/W3 won't run > because somebody is treating a keyword as a variable. Haven't been > able to figure out where though. Bleah. Uhm. (setq debug-on-error t)? Note that in XEmacs it's legal to say (setq :foo :foo). (setq :foo :bar) signals an error, though.

1 participants
0 comments

Re: M-up and M-down changed? 25 years

Hrvoje Niksic

Ben Wing <ben(a)666.com> writes: > Comments? I realize now that I definitely should have discussed > this more before going ahead and making the changes, but it seemed > to me that nobody cared much about the arrow keys, given the sorry > state (from my obviously biased perspective) they were in. I can certainly live with your changes. In fact, I use M-a and M-e extremely often (more often than M-up and M-down, which I also use), and I'll try to retrain my fingers to use M-up and M-down instead. The point is that _any_ key binding change has a potential for being controversial. We'll see wat happens when more beta testers start using XEmacs with your changes.

1 participants
0 comments

Re: 25 years

William M. Perry

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Andy Piper <andy(a)xemacs.org> writes: > > > ? Its got to live in core. Anything that doesn't work with just a core > > XEmacs is as useless as efs. Having to install w3 and gnus is less than > > useless. Maybe I'm misunderstanding... > > I think he just meant that if we upgrade to new URL stuff (which could > be in the core) we have to upgrade the w3 and Gnus package at the same > time because of all the interdependencies. Yup, that is what I meant. > That's no so big a problem (at least not technically) Well, other than that the current version of Emacs/W3 won't run because somebody is treating a keyword as a variable. Haven't been able to figure out where though. Bleah. -bp

1 participants
0 comments

Re: 25 years

Jan Vroonhof

Andy Piper <andy(a)xemacs.org> writes: > ? Its got to live in core. Anything that doesn't work with just a core > XEmacs is as useless as efs. Having to install w3 and gnus is less than > useless. Maybe I'm misunderstanding... I think he just meant that if we upgrade to new URL stuff (which could be in the core) we have to upgrade the w3 and Gnus package at the same time because of all the interdependencies. That's no so big a problem (at least not technically) Jan

1 participants
0 comments

Re: EUDC crash with 21.2.31 on Solaris 2.7 25 years

Jan Vroonhof

Raymond Toy <toy(a)rtp.ericsson.se> writes: > I tried it again, except I set always_gc a bit earlier. It runs > forever, eventually producing an error message: Wrong type: listp: > ?o. But xemacs doesn't crash. Still some signs of weird memory corruption.. I don't know any easy debugging tricks now either.. Jan

1 participants
0 comments

[CRASH] 21.2.31 Closing Ediff frame. 25 years

Yoshiki Hayashi

(emacs-version) "XEmacs 21.2 (beta31) \"Iris\" [Lucid] (i686-pc-linux, Mule) of Wed Mar 15 2000 on buck" When I typed "q y" in Ediff control buffer, XEmacs crashed. I cannot reproduce it. Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. If you have access to the PROBLEMS file that came with your version of XEmacs, please check to see if your crash is described there, as there may be a workaround available. Otherwise, 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 /opt/local/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: # (condition-case ... . error) # (catch top-level ...) (gdb) bt #0 0x4040d911 in kill () from /lib/libc.so.6 #1 0x80c21bd in fatal_error_signal (sig=11) at emacs.c:272 #2 0x4040d848 in sigaction () from /lib/libc.so.6 #3 0x81ede49 in x_event_to_emacs_event (x_event=0xbffff59c, emacs_event=0x92d5a08) at event-Xt.c:1170 #4 0x81f0ccb in emacs_Xt_event_handler (wid=0x9490530, closure=0x0, event=0xbffff59c, continue_to_dispatch=0xbffff48b "\001") at event-Xt.c:2619 #5 0x40212b6d in XtDispatchEventToWidget () from /usr/X11R6/lib/libXt.so.6 #6 0x402134ee in _XtOnGrabList () from /usr/X11R6/lib/libXt.so.6 #7 0x40213738 in XtDispatchEvent () from /usr/X11R6/lib/libXt.so.6 #8 0x4021df51 in XtAppProcessEvent () from /usr/X11R6/lib/libXt.so.6 #9 0x81ef933 in emacs_Xt_next_event (emacs_event=0x92d57c4) at event-Xt.c:2571 #10 0x8113c00 in event_stream_next_event (event=0x92d57c4) at event-stream.c:501 #11 0x8115ae9 in next_event_internal (target_event=153966532, allow_queued=1) at event-stream.c:1960 #12 0x811604d in Fnext_event (event=153966532, prompt=137204316) at event-stream.c:2174 #13 0x80a54b7 in Fcommand_loop_1 () at cmdloop.c:565 #14 0x80a5783 in command_loop_1 (dummy=137204316) at cmdloop.c:490 #15 0x80c42b4 in condition_case_1 (handlers=137204412, bfun=0x80a5740 <command_loop_1>, barg=137204316, hfun=0x80a4910 <cmd_error>, harg=137204316) at eval.c:1644 #16 0x80a58b4 in command_loop_2 (dummy=137204316) at cmdloop.c:252 #17 0x80c4093 in internal_catch (tag=137278436, func=0x80a5870 <command_loop_2>, arg=137204316, threw=0x0) at eval.c:1309 #18 0x80a4d0a in initial_command_loop (load_me=137204316) at cmdloop.c:301 #19 0x80c03d1 in xemacs_21_2_b31_i686_pc_linux () at emacs.c:1828 #20 0x80c0c1f in main () at emacs.c:2254 #21 0x40407a42 in __libc_start_main () from /lib/libc.so.6 uname -a: Linux buck 2.2.14 #4 Sun Mar 12 10:02:54 JST 2000 i686 unknown ./configure '--prefix=/opt/local' '--with-mule' '--site-includes=/usr/include/postgresql' '--with-canna=no' '--with-wnn=no' XEmacs 21.2-b31 "Iris" configured for `i686-pc-linux'. Where should the build process find the source code? /src/xemacs What installation prefix should install use? /opt/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 -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/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Additional header files: /usr/include/postgresql 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 LDAP. Compiling in support for PostgreSQL. Compiling in support for ncurses. 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 proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Motif native widgets. Using Motif dialog boxes. Compiling in dynamic shared object module support. movemail will use "dot-locking" for locking mail spool files. 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: --------------------------------------------------------- -- Yoshiki Hayashi

1 participants
0 comments

Progress gauge crash 25 years

Hrvoje Niksic

I've tried to replace (sit-for 0.5) with (sit-for 0), and encountered a crash. Lisp backtrace: redisplay-frame() # bind (inhibit-read-only zmacs-region-stays val frame value message) raw-append-progress("Fontifying *followup to Kai Großjohann on gnu.emacs.gnus*..." 0 #<x-frame "Gnus" 0x64f7>) (if (eq label (car top)) (progn (setcdr top message) (if ... ... ...) (redisplay-gutter-area)) (push (cons label message) progress-stack) (raw-append-progress message value frame)) ) # bind (tmsg top) (let* ((top ...) (tmsg ...)) (if (eq label ...) (progn ... ... ...) (push ... progress-stack) (raw-append-progress message value frame)) (dispatch-non-command-events) (when (input-pending-p) (dispatch-event ...)) (when (eq value 100) (sit-for 0 nil) (clear-progress label))) ) # bind (frame value message label) append-progress(font-lock "Fontifying *followup to Kai Großjohann on gnu.emacs.gnus*..." 0 nil) # bind (frame value message label) display-progress(font-lock "Fontifying *followup to Kai Großjohann on gnu.emacs.gnus*..." 0) # bind (str args value fmt label) lprogress(font-lock "Fontifying %s..." 0 "*followup to Kai Großjohann on gnu.emacs.gnus*") # bind (maybe-loudly end beg) font-lock-default-unfontify-region(1 1 t) # bind (loudly end beg) font-lock-unfontify-region(1 1 t) # bind (was-on font-lock-verbose font-lock-message-threshold aborted) font-lock-default-fontify-buffer() # bind (font-lock-verbose) font-lock-fontify-buffer() # bind (on-p maximum-size arg) font-lock-mode(1) turn-on-font-lock() # bind (explicit-defaults) font-lock-set-defaults() message-xmas-maybe-fontify() run-hooks(text-mode-hook-identify message-xmas-maybe-fontify) message-mode() ... C backtrace:

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