August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

more misc gutter patches 24 years, 8 months

Andy Piper

This should make things a bit better. Thanks to those who are being crash test dummies (Kyle has all the good catch-phrases). I will commit this. andy 1999-08-05 Andy Piper <andy(a)xemacs.org> * glyphs.c (check_for_ignored_expose): ignore exposures wholly contained in our ignore list. * gutter-items.el (update-tab-in-gutter): add frame argument for buffer-items. (update-tab-in-gutter): use it. * buffer.c (Frecord_buffer): add call to record-buffer-hook. (syms_of_buffer): declare record-buffer-hook. * gutter-items.el (record-buffer-hook): set. * buffer.el (switch-to-buffer): back out switch-to-buffer-hook change. (switch-to-buffer-hook) deleted. -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

Re: [BUG] 21.2.19+ --with-widget configure problems, /usr/dt is poison 24 years, 8 months

SL Baur

Andy Piper <andy(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > At 01:44 PM 8/3/99 +0900, SL Baur wrote: >> Configuring with --with-widgets=athena3d results in no widgets. > How did you determine this. By examination of the output in the Installation file. > Did it just not say anything or did you look at config.h? The former > is expected (and fixed now), the latter is not. I have synched with your latest changes and will try again. [...] O.K. I have just reconfigured and the Installation output is busted, however src/config.h sez: #define LWLIB_WIDGETS_ATHENA 1 Please make sure the summary stuffs get fixed. It is vital that it contains accurate information about what is being built into XEmacs. ... >> make[1]: *** [lwlib-Xm.o] Error 1 >> make[1]: Leaving directory `/usr/local/devel/miho-test/lwlib' >> make: *** [lwlib] Error 2 > Ok I've fixed this I think. I am doing an Athena test build to try it out. uname -a: SunOS miho 5.6 Generic_105181-05 sun4u sparc ../xemacs-21.2/configure '--with-mule' '--debug=yes' '--error-checking=all' '--extra-verbose=no' '--site-prefixes=/usr/local' '--compiler=gcc' '--mail-locking=file' '--srcdir=../xemacs-21.2' '--cflags=-g -O3' '--site-includes=/usr/lib/locale/ja/wnn/demo/include' '--site-libraries=/usr/lib/locale/ja/wnn/lib' '--with-scrollbars=athena3d' '--with-dialogs=athena3d' '--with-xim=none' '--with-widgets=athena3d' XEmacs 21.2-b19 "Shinjuku" configured for `sparc-sun-solaris2.6'. Where should the build process find the source code? /usr/local/devel/xemacs-21.2 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? gcc -g -O3 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/dt/include /usr/local/X11R6/include Where do we find X Windows libraries? /usr/dt/lib /usr/local/X11R6/lib Additional header files: /usr/lib/locale/ja/wnn/demo/include Additional libraries: /usr/lib/locale/ja/wnn/lib Additional prefixes: /usr/local Runtime library search path: /usr/lib/locale/ja/wnn/lib:/usr/local/lib:/usr/dt/lib:/usr/local/X11R6/lib:/usr/local/qt/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 support for X-Face message headers. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in support for Canna on Mule. Compiling in support for the WNN input method on Mule. Using WNN version 6. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in EXPERIMENTAL support for Drag'n'Drop ( CDE ). Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Athena-3d scrollbars. Using Athena-3d dialog boxes. Compiling in DSO 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: ---------------------------------------------------------

2 participants
1 comments

Re: [BUG] 21.2.19+ --with-widget configure problems, /usr/dt is poison 24 years, 8 months

SL Baur

SL Baur <steve(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > Andy Piper <andy(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: >> At 01:44 PM 8/3/99 +0900, SL Baur wrote: >>> Configuring with --with-widgets=athena3d results in no widgets. >> How did you determine this. > By examination of the output in the Installation file. >> Did it just not say anything or did you look at config.h? The former >> is expected (and fixed now), the latter is not. > I have synched with your latest changes and will try again. [...] > O.K. I have just reconfigured and the Installation output is busted, > however src/config.h sez: > #define LWLIB_WIDGETS_ATHENA 1 > Please make sure the summary stuffs get fixed. It is vital that it > contains accurate information about what is being built into XEmacs. Oops. Sorry. This statement is inoperative. I hadn't completely synched up. When I did a fresh update, the option showed up properly in the summary.[1] The other two problems I described (continual refresh when updating tabs in a partially obscured frame) and the missing separator line when `C-x o'ing to a window without a tab are still there. Footnotes: [1] Q: Why do blondes have flat foreheads? A: [slapping himself on the forehead] I don't know!

1 participants
0 comments

Re: package manager misuses pgp5, and fails with pgp2.6.2, too 24 years, 8 months

SL Baur

Karl Kleinpaste <karl(a)justresearch.com> writes in xemacs-beta(a)xemacs.org: > SL Baur <steve(a)xemacs.org> writes: >> It depends upon which version of the package-index file you are using. > Offhand, I didn't even know what package-index was in question. I > already had the July 29 sumo tarballs installed, and was just toying > with the package manager when I ran into this bug. As it happens, I > just now manually acquired the latest mailcrypt-2.02 package and > installed it...and now when I run the exact same sequence in an > "xemacs -q", it claims that entries are not signed at all. This is > notwithstanding the fact that I now have a package-index.LATEST.pgp > with modtime of just moments ago, plus the prev. version as > package-index.LATEST.pgp~, with modtime July 29 21:50. > ??? Right. Jan Vroonhof has been having me do that for some number of releases now to bypass mailcrypt signature checking problems. I think the current situation is hopeless and I give up. >> You can either strip out the signature, or update to the most recent >> package-index file on the FTP site (which includes a pointer to an >> updated version of the mailcrypt package). > As I said, I already got that later mailcrypt. But I have no idea how > or why any of this has occurred. Installing the latest mailcrypt > shouldn't have affected the determination of *whether* the packages > are PGP-signed. In fact, now, after starting up the package manager > (and telling it to continue even though entries are not signed), the > mailcrypt library is not even loaded -- the variable mc-version is not > known. > I am *so* confused. As am I. I now have a pgp 2.6.3 binary built from sources off of replay.com. Should I try signing with that version instead?

1 participants
0 comments

bad change to buffer-string 24 years, 8 months

William M. Perry

You used to be able to do (buffer-string nil nil somebuffer) to get the entire string out of a buffer. With XEmacs 21.2, it has been changed to just take a 'buffer' arguent, but it is _supposed_ to be backwards compatible and take 'buffer old-end old-buffer' arguments. But if you pass in nil for 'buffer', it thinks you want the new way and 'nil' means current-buffer. This broke the content-id (cid) url handling in Emacs/W3 + pGnus. The offending code is: ;; This function used to be an alias to `buffer-substring', except ;; that FSF Emacs 20.4 added a BUFFER argument in an incompatible way. ;; The new FSF's semantics makes more sense, but we try to support ;; both for backward compatibility. (defun buffer-string (&optional buffer old-end old-buffer) "Return the contents of the current buffer as a string. If narrowing is in effect, this function returns only the visible part of the buffer. If BUFFER is specified, the contents of that buffer are returned. The arguments OLD-END and OLD-BUFFER are supported for backward compatibility with pre-21.2 XEmacsen times when arguments to this function were (buffer-string &optional START END BUFFER)." (if (or (null buffer) (bufferp buffer) (stringp buffer)) ;; The new way (buffer-substring nil nil buffer) ;; The old way (buffer-substring buffer old-end old-buffer))) I think this would be better written as: (cond ((or (stringp buffer) (bufferp buffer)) ;; most definitely the new way (buffer-substring nil nil buffer)) ((or (stringp old-buffer) (bufferp old-buffer) (natnump buffer) (natnump old-end)) ;; definitely the old way (buffer-substring buffer old-end old-buffer)) (t ;; probably the old way (buffer-substring buffer old-end old-buffer))) Might be a little more robust and preserve the old behaviour in the 'nil nil buff' case. -bp

1 participants
0 comments

Re: 21.2.19 SEGV on null frame pointer 24 years, 8 months

Karl Kleinpaste

[ sending this note back to the list, per private requests ] Kyle (and others), it didn't take long... XEmacs was started thus: xemacs -geometry 207x89+1282+0 -f gnus-init where "gnus-init" is just a small wrapper around Gnus' start-up for me: (defun gnus-init () "Start Gnus and smallify." (interactive) (gnus-no-server) (x-active-icon-toggle nil)) The exact keyboard sequence that had occurred when the SEGV was taken was that I was reading comp.emacs.xemacs (hm! :-), and I exited with a common set of keystrokes for me: q l < s g In Gnus, that means - quit the group - reduce the listed group set to only those with unread articles - goto the top of the *Group* buffer - save .newsrc* - get new news This is a very common key sequence for me; I do it a lot when I notice mail arriving via xbiff and want to go get it. I type that sequence a lot, and quickly. Significantly, there was - no mouse activity - no window manager activity Just keystrokes, maneuvering with bland Gnus command bindings. Gnus didn't even get as far as carrying out the `l' list-reduction command. It cleaned out the *Summary* buffer, leaving only *Group* showing, still cluttered with zero-message groups showing, and then stopped in gdb on SEGV. The stack trace is the same: SEGV thrown on 259 assert (EQ (FRAME_TYPE (f), sym)); I'm a little confused by the stack, considering that this is an inline func in frame.h; the next stack frame shows x_event_to_emacs_event() at a line where it's calling x_to_emacs_keysym()...there must be some macro call which gets to error_check_frame_type() somehow, but I don't see it right this instant. I'm leaving this (dying) XEmacs attached to the gdb which caught it, so I am open to suggestions for things to look at. Anything you'd like to see pobj'd...? --karl

2 participants
1 comments

RE: 21.2-b19: hang under Solaris 2.5.1 24 years, 8 months

Damon Lipparelli

For what it's worth, I was able to build and run things under Solaris 2.6 (and X11R6). -lipp -----Original Message----- From: Andy Piper [mailto:andy＠xemacs.org] Sent: Wednesday, August 04, 1999 12:59 PM To: Damon Lipparelli; 'xemacs-beta(a)xemacs.org' Subject: RE: 21.2-b19: hang under Solaris 2.5.1 At 09:24 AM 8/4/99 -0700, Damon Lipparelli wrote: >I was wondering & thinking the same things. Any investigation you want me >to try? Yes, but what - I have no idea :) Is it you using X11R5? If so can you try commenting out the handle_focus_1 changes I put in for widgets to see if that fixes anything? Thanks andy -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

RE: 21.2-b19: hang under Solaris 2.5.1 24 years, 8 months

Damon Lipparelli

The Solaris installation I'm using still has X11R5. Assuming you meant handle_focus_event_1 (in "event-Xt.c"), I just tried commenting out all calls to it. It's still hanging and the stack trace (appended) looks the same. -lipp ps: When I try invoking "src/xemacs -batch -vanilla -f batch-byte-compile" on one of the files that it is trying to build when it hangs, XEmacs returns after a second or so without a complaint, but no ".elc" file isn't produced. -----Original Message----- From: Andy Piper [mailto:andy＠xemacs.org] Sent: Wednesday, August 04, 1999 12:59 PM To: Damon Lipparelli; 'xemacs-beta(a)xemacs.org' Subject: RE: 21.2-b19: hang under Solaris 2.5.1 At 09:24 AM 8/4/99 -0700, Damon Lipparelli wrote: >I was wondering & thinking the same things. Any investigation you want me >to try? Yes, but what - I have no idea :) Is it you using X11R5? If so can you try commenting out the handle_focus_1 changes I put in for widgets to see if that fixes anything? Thanks andy -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

Re: 21.2.19 SEGV on null frame pointer 24 years, 8 months

Karl Kleinpaste

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Can you remembner roughly what you are doing when the crash happens? > Clicking and dragging? Moving the mouse? Using the toolbar? It always occurs in the XEmacs in which I run Gnus; I've never seen it occur when not running Gnus. Generally speaking, my recollection is that it occurs when doing a series of command keystrokes in rapid succession. I know it has occurred once or twice in recent weeks when shifting via Ctrl-<arrow> keys into the fvwm2 pane where XEmacs lives (so the first event to handle is the need to redraw) and then hitting a couple keystrokes right away. For possibility exclusions: - I don't click-n-drag enough to know about, so that wouldn't be it. - I also don't use the toolbar appreciably. - All in all, I tend not to use the mouse a great deal, being a keyboard-centric sort of fellow. It'll happen again in a day or two at the most, I'm sure. I'll make sure to give some careful thought to exactly what Gnus was doing, and how I was ordering it about at the time. I'll drop you a note privately next time around. And thanx for the response. --karl

1 participants
0 comments

21.2.19 SEGV on null frame pointer 24 years, 8 months

Karl Kleinpaste

Does anyone care about this error at all? I don't do X internals much at all, never have, never really cared to. I've been reporting this occasionally since I first began using 21.2, around -b6 I believe, in the hope that someone might at least have an idea of what add'l info I could dredge up when it happens, to help identify the flaw. Still happens, once or twice a week -- something is misusing a null frame pointer as a consequence of Xt event handling. --karl Program received signal SIGSEGV, Segmentation fault. x_to_emacs_keysym (event=0x7ffff508, simple_p=0) at frame.h:259 259 assert (EQ (FRAME_TYPE (f), sym)); (gdb) bt #0 x_to_emacs_keysym (event=0x7ffff508, simple_p=0) at frame.h:259 #1 0x81b45d4 in x_event_to_emacs_event (x_event=0x7ffff508, emacs_event=0x8967280) at event-Xt.c:999 #2 0x81b67d3 in emacs_Xt_event_handler (wid=0x85b3528, closure=0x0, event=0x7ffff508, continue_to_dispatch=0x7ffff443 "\001ÀtP\b,") at event-Xt.c:2470 #3 0x2ab9cc9f in XtDispatchEventToWidget () #4 0x2ab9d6fd in _XtDefaultDispatcher () #5 0x2ab9d975 in XtDispatchEvent () #6 0x2aba83d5 in XtAppProcessEvent () #7 0x81b6f3f in emacs_Xt_event_pending_p (user_p=1) at event-Xt.c:2626 #8 0x80da8bd in detect_input_pending () at event-stream.c:945 #9 0x80dce11 in Fnext_event (event=146267928, prompt=137162676) at event-stream.c:2237 #10 0x807330e in Fcommand_loop_1 () at cmdloop.c:569 #11 0x807309d in command_loop_1 (dummy=137162676) at cmdloop.c:493 #12 0x8091785 in condition_case_1 (handlers=137162772, bfun=0x807304c <command_loop_1>, barg=137162676, hfun=0x80724d0 <cmd_error>, harg=137162676) at eval.c:1640 #13 0x8073538 in command_loop_2 (dummy=137162676) at cmdloop.c:255 #14 0x8091360 in internal_catch (tag=137236964, func=0x8073504 <command_loop_2>, arg=137162676, threw=0x0) at eval.c:1315 #15 0x8072937 in initial_command_loop (load_me=137162676) at cmdloop.c:304 #16 0x808cfa1 in xemacs_21_2_b19_i686_pc_linux (argc=5, argv=0x7ffff994, envp=0x7ffff9ac, restart=0) at emacs.c:1763 #17 0x808d72d in main (argc=5, argv=0x7ffff994, envp=0x7ffff9ac) at emacs.c:2188 (gdb) list 254 INLINE struct frame * 255 error_check_frame_type (struct frame * f, Lisp_Object sym); 256 INLINE struct frame * 257 error_check_frame_type (struct frame * f, Lisp_Object sym) 258 { 259 assert (EQ (FRAME_TYPE (f), sym)); 260 return f; 261 } 262 # define FRAME_TYPE_DATA(f, type) \ 263 ((struct type##_frame *) (error_check_frame_type (f, Q##type))->frame_data) (gdb) p f $1 = (struct frame *) 0x0 uname -a: Linux beaver.jprc.com 2.2.10-ac10 #1 SMP Tue Jul 13 13:23:27 EDT 1999 i686 unknown ./configure '--with-pop' '--with-mule' '--with-png' XEmacs 21.2-b19 "Shinjuku" configured for `i686-pc-linux'. Where should the build process find the source code? /home/karl/src/x/xemacs-21/xemacs-21.2.19 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 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 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 Berkeley DB. Compiling in support for GNU DBM. 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 proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DSO module support. movemail will use "dot-locking" for locking mail spool files. Using POP for mail access. 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: ---------------------------------------------------------

2 participants
1 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 August 1999