August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: new bug in hm--html-menus 24 years, 9 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)srce.hr> writes: > > You are not allowed to call X functions during bytecompilation (nor > > any other feature specific call). > > I don't have the hm-- stuff around, so I can't fix the problem. I do > remember that someone changed the code in question lately, so > investigating that change should lead to the problem. I did. I even used that function. However it used in this way(see below), not called. Are the cl macros getting in the way? Jan [for a few hours back from usenet-death] (if (adapt-xemacsp) (progn (defvar hm--html-gpmr (symbol-function 'get-popup-menu-response)) (defun hm--html-call-wrapped-sgml-menu (event) (flet ((get-popup-menu-response (menudesc &optional event) (setq menudesc (append hm--html-popup-menu (list "==" (car menudesc) "==") (cdr menudesc))) (setq event (funcall hm--html-gpmr menudesc event)) (if (and (misc-user-event-p event) (commandp (event-object event)) (boundp 'hm--html-mark)) (progn (set-mark hm--html-mark) (goto-char hm--html-point) (call-interactively (event-object event))) event))) (sgml-tags-menu event)))

1 participants
0 comments

Re: vc-revert-buffer1 sacrifices fontification preserving minor modes 24 years, 9 months

Jan Vroonhof

Raymond Toy <toy(a)rtp.ericsson.se> writes: > APA> Which font-locking method do we want to promote? > > But lazy-shot has the same font-locking problem: revert-buffer > doesn't fontify the buffer. Yes, but I am fairly sure it can be fixed. In fact I am not sure it is lazy-shot's fault at all. lazy-shot's logic is extremely simple, that is why it so nice compared to lazy-lock. That particular change to font-lock should be revisited and consequences checked. I for my part find it very suspect that the font-lock-revert-cleanup as been defined to nothing but the font-lock-revert-setup hooks hasn't. Jan [for a few hours back from usenet-death]

1 participants
0 comments

Re: vc-revert-buffer1 sacrifices fontification preserving minor modes 24 years, 9 months

Jan Vroonhof

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > sb> If we must recommend defaulting to lazy font-locking, then it should > sb> probably be the lazy-shot flavor. At least that version works in an > sb> XEmacs-y sort of way. > > Which font-locking method do we want to promote? lazy-shot. That is what the Options menu lazy-settings does. Jan [for a few hours back from usenet-death]

1 participants
0 comments

Re: current-pixel-column 24 years, 9 months

William M. Perry

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > William M. Perry writes: > > Andy Piper <andy(a)xemacs.org> writes: > > > > > How about this? > > > > How about one for passing in an arbitrary buffer position, not just > > current-point? > > A buffer isn't specific enough. You have to specify the window > to use. That's what I meant. :) -bp

1 participants
0 comments

current-pixel-column 24 years, 9 months

Andy Piper

How about this? andy 1999-08-05 Andy Piper <andyp(a)beasys.com> * window.c (Fcurrent_pixel_column): new function. use display lines to calculate pixel position of point. * window.c (syms_of_window): declare it. -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

regexp-opt 24 years, 9 months

Olivier Galibert

regexp-opt is for now part of xemacs-devel, which mean usually not installed by non xemacs-developers. Bad thing is, it is used by make-mode.el without even a require. What is the right fix? OG.

1 participants
0 comments

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

Gunnar Evermann

Karl Kleinpaste <karl(a)justresearch.com> writes: > 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. Yes I see something very similar. To me it also only happens in gnus and especially often when I hit a couple of keys in gnus and then switch the virtual (fvwm2) desktop. Typically it's 'c y s' from a summary buffer and I switch desktops while Gnus is still marking the messages as read. I posted a summary of what I gleamed from the core dumps a long time ago. see <m33e0xbcl2.fsf(a)oracle.local.net> on xemacs-beta. basically x_any_window_to_frame() couldn't find the window in any frame. Gunnar

1 participants
0 comments

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

Karl Kleinpaste

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Karl, I'm interested in seeing f->framemeths->symbol and sym. Well, the whole reason for the SEGV is that f is 0x0. See Subject:. :-) gdb complains that it does not know of a "sym" in this context. I'm trying to chase through the twisty maze of #definitions and inline func defs to figure out how gdb would comprehend what is being called "sym" here, but so far... Er, hang on, I think I just got it. Or got something, anyway. The FRAME_TYPE_DATA whose assertion is getting horked over on a null pointer is actually the FRAME_X_XIC at the top of x_to_emacs_keysym(), line 783, assuming I've followed the twisty maze properly. (gdb) p event->window $16 = 79692505 (gdb) p event->display $17 = (Display *) 0x85074c0 (gdb) p *(event->display) $18 = <incomplete type> (gdb) p get_device_from_display (event->display) $19 = (struct device *) 0x832cf10 (gdb) p x_any_window_to_frame(get_device_from_display (event->display),event->window) $20 = (struct frame *) 0x0 I just single-stepped through that call of x_any_window_to_frame. It just plain didn't find a frame it liked. It did check a frame on the way through (which does have symbol 'x), but it didn't think that was the right one. (gdb) p x_any_window_to_frame(get_device_from_display (event->display),event->window) Breakpoint 1, x_any_window_to_frame (d=0x832cf10, wdesc=79692505) at frame-x.c:109 109 assert (DEVICE_X_P (d)); The program being debugged stopped while in a function called from GDB. When the function (x_any_window_to_frame) is done executing, GDB will silently stop (instead of continuing to evaluate the expression containing the function call). (gdb) n 145 return f; (gdb) 119 frame = XCAR (tail); (gdb) 120 f = XFRAME (frame); (gdb) 122 if (wdesc == XtWindow (FRAME_X_SHELL_WIDGET (f)) || (gdb) p frame $39 = 140188784 (gdb) p f $40 = (struct frame *) 0x85b1c70 (gdb) pobj f->framemeths->symbol $41 = (Lisp_Symbol *) 0x82ecd24 $42 = {lheader = {type = 3, mark = 0, c_readonly = 0, lisp_readonly = 0}, next = 0x0, name = 0x82ec59c, value = 136654664, function = 136654664, plist = 146629516} Symbol name: x (gdb) n 124 wdesc == XtWindow (FRAME_X_TEXT_WIDGET (f))) (gdb) 141 for (i = 0; i < FRAME_X_NUM_TOP_WIDGETS (f); i++) (gdb) 143 Widget wid = FRAME_X_TOP_WIDGETS (f)[i]; (gdb) 144 if (wid && XtIsManaged (wid) && wdesc == XtWindow (wid)) (gdb) 146 } (gdb) 259 assert (EQ (FRAME_TYPE (f), sym)); (gdb) 141 for (i = 0; i < FRAME_X_NUM_TOP_WIDGETS (f); i++) (gdb) 150 if (x_window_is_scrollbar (f, wdesc)) (gdb) 153 } (gdb) 155 return 0; (gdb) 156 } (gdb) > Also please print Qt, Qnil, and Qx for reference. (gdb) pobj Qt $6 = (Lisp_Symbol *) 0x82cefcc $7 = {lheader = {type = 3, mark = 0, c_readonly = 0, lisp_readonly = 0}, next = 0x0, name = 0x82ce7cc, value = 137162700, function = 136654664, plist = 145957396} Symbol name: t (gdb) pobj Qnil $8 = (Lisp_Symbol *) 0x82cefb4 $9 = {lheader = {type = 3, mark = 0, c_readonly = 0, lisp_readonly = 0}, next = 0x0, name = 0x82ce7bc, value = 137162676, function = 136654664, plist = 137162676} Symbol name: nil (gdb) pobj Qx $10 = (Lisp_Symbol *) 0x82ecd24 $11 = {lheader = {type = 3, mark = 0, c_readonly = 0, lisp_readonly = 0}, next = 0x0, name = 0x82ec59c, value = 136654664, function = 136654664, plist = 146629516} Symbol name: x --karl

1 participants
0 comments

Re: gutter fixes 24 years, 9 months

Adrian Aichner

>>>>> "Andy" == Andy Piper <andy(a)xemacs.org> writes: >> I get more and more confused about which buffers are supposed to have >> tabs. Is there a spec for this feature? Andy> Its currently simple. You should get a tab for every buffer Andy> in (buffer-list), anything else is a bug - so you are seeing Andy> lots of bugs. The patch I have just commited should make Andy> this a lot better...... Hi Andy, shouldn't gutters with default location bottom look like this? ___ _________ |___| M-x show-message-log Bottom gutters currently appear as ___ ___| |_________ M-x show-message-log (just like in the top location) which visually associates them with the minibuffer. Adrian

2 participants
1 comments

[SHAKY] 21.2 (beta19) "Shinjuku" XEmacs Lucid on i686-pc-linux 24 years, 9 months

Jason R. Mastaler

Shinjuku builds without any problems. The buffer buttons are cool, but visually disconcerting during refresh. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /home/jason/xemacs/beta/build/Installation: > (Output from most recent run of ./configure) uname -a: Linux bodhi.mastaler.com 2.2.5-15 #1 Mon Apr 19 23:00:46 EDT 1999 i686 unknown /usr/local/src/xemacs-21.2/configure '--prefix=/home/jason/xemacs/beta/v21' '--package-path=/home/jason/xemacs/beta/packages' '--with-dialogs=athena3d' '--with-sound=native' '--mail-locking=flock' '--with-mule' '--error-checking=none' '--debug=no' XEmacs 21.2-b19 "Shinjuku" configured for `i686-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21.2 What installation prefix should install use? /home/jason/xemacs/beta/v21 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 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-3d dialog boxes. Compiling in DSO module support. movemail will use "flock" for locking mail spool files. > /home/jason/xemacs/beta/build/beta.err does not exist!

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