January 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Hrvoje Niksic

If I understand things correctly, the preferred way to add stuff to Info directory search path is using `Info-directory-list', e.g.: (push "~/my-info-dir" Info-directory-list) or: (setq Info-directory-list (append '("dir1" "dir2" "dir3") Info-directory-list)) This works in .emacs because Info-directory-list is autoloaded rather than set in info.el. The documentation says: The first directory in this list, the "dir" file there will become the (dir)Top node of the Info documentation tree. If you wish to modify the info search path, use `M-x customize-variable, Info-directory-list' to do so. The last sentence is IMO wrong: if you change the value of the variable, you will completely override the autoloaded defaults. This means that if the autoloaded stuff changes, e.g. by installing a new package, the new values get ignored. Info-directory-list should not be customizable at all.

1 participants
0 comments

Re: Merging customize support 25 years

Didier Verna

Hrvoje Niksic wrote: > You should mail patches to <xemacs-patches(a)xemacs.org>. I suppose it > could be arranged that your customize-related patches are > automatically approved. You could also have CVS write access and > commit your changes yourself. Actually, both solutions should be arranged for Per: he should post to xemacs-patches as it is the policy everybody follows (even reviewers) AND be able to commit by himself. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99

1 participants
0 comments

Re: Merging customize support 25 years

Hrvoje Niksic

Per Abrahamsen <abraham(a)dina.kvl.dk> writes: > Hrvoje Niksic <hniksic(a)iskon.hr> writes: > > > You could also have CVS write access and commit your changes > > yourself. > > That would be most convenient. If so, I'll suggest changes on > <emacs-custom(a)sunsite.auc.dk>, and if nobody protest, commit them to > both Emacs and XEmacs. You should still Cc the actual patch to <xemacs-patches(a)xemacs.org>, as it's the custom (no pun intended) for everyone. > Who should I mail cvs username and password to? After this is approved by the maintainers, that would be Jason Mastaler <jason(a)xemacs.org>.

1 participants
0 comments

[21.2.26] assertion in redisplay.c 25 years

Marcus Thiessel

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 (beta26) "Millenium" [Lucid] (hppa1.1-hp-hpux11.00, Mule) of Sat Jan 1 2000 on tmbbwmt configured using `configure hppa1.1-hp-hpux11.00 --dynamic=no --prefix=/usr/local/xemacs --with-x --with-dialogs=motif --with-xface=yes --with-tty=yes '--x-includes=/usr/include/Motif2.1 -I/usr/include/X11R6' '--x-libraries=/usr/lib/Motif1.2_R6 -L/usr/lib/X11R6' --with-database=dbm --with-pop --mail-locking=lockf '--site-includes=/usr/contrib/include -I/usr/local/include' --error-checking=none --extra-verbose '--site-libraries=/usr/contrib/lib -L/usr/local/lib' --with-sound=no --with-xmu --with-mule=yes --with-cde=yes --with-tooltalk=yes --with-gcc=no --package-path=/opt/src/packages '--cflags=+DS2.0 +DA1.1 +O3 +ESlit +Oloop_transform +Odataprefetch +Onolimit +Oprocelim +Olibcalls +Ofastaccess'' While pressing a button in the Ediff window (toolbar enabled) I got Fatal error: assertion failed, file redisplay.c, line 7516, abort() Fatal error (6). Your files have been auto-saved. Lisp backtrace follows: event-window(#<motion-event 45, 9>) # bind (frame event) default-mouse-motion-handler(#<motion-event 45, 9>) # (condition-case ... . error) # (catch top-level ...)

1 participants
0 comments

Re: Merging customize support 25 years

Hrvoje Niksic

Per Abrahamsen <abraham(a)dina.kvl.dk> writes: > 2) Letting me try to bring to two code bases closer to each other. > I got more or less free hands for that. > > My goal is that the only differences should be either due to > differences in the underlying mechanism (mostly hidden in > cus-face.el and the widget abstraction) or different UI style > preferences (mostly manifested as different standard values for user > options). Yes. > I'd like to know if XEmacs people agree to these ideas, and if so, > how changes from me to the XEmacs customize implementation should be > handled. You should mail patches to <xemacs-patches(a)xemacs.org>. I suppose it could be arranged that your customize-related patches are automatically approved. You could also have CVS write access and commit your changes yourself.

1 participants
0 comments

Re: Merging customize support 25 years

Per Abrahamsen

I took it up with Gerd, D.Love and RMS. They agreed my proposal to 1) Using <emacs-custom(a)sunsite.auc.dk>. as a shared Emacs/XEmacs forum for discussion changes to customize. I have added Gerd and D.Love to the list, I think all the XEmacs customize maintainers are already on it, if not, subscribe by sending a mail to <emacs-custom-subscribe(a)sunsite.auc.dk>. 2) Letting me try to bring to two code bases closer to each other. I got more or less free hands for that. My goal is that the only differences should be either due to differences in the underlying mechanism (mostly hidden in cus-face.el and the widget abstraction) or different UI style preferences (mostly manifested as different standard values for user options). ... I'd like to know if XEmacs people agree to these ideas, and if so, how changes from me to the XEmacs customize implementation should be handled.

1 participants
0 comments

Re: `yes-or-no-p-dialog-box' crash - Aborts. 25 years

Karl M. Hegbloom

>>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: Stephen> Lots and lots of widget leaks there, as far as I can Stephen> tell; haven't had a chance to look carefully, but it Stephen> doesn't take long to get a couple copies of scrollbars Stephen> and multiple copies of the tabs widget with only one Stephen> frame up. (XEmacs CVS updated around the release of Stephen> 21.2.25, more or less, I think I rebuilt on that box Stephen> since then :-/ .) I wonder if that's what locked up my machine several times in the last few months. Just the other day, something started paging... I wasn't really paying any attention, until I happened to glance over at the Mem and Swap needles on a `gkrellm' I keep running... The swap meter had climbed until almost pegged, and the next thing I knew, everything locked up solid. I had to power cycle. XEmacs was running at the time... the cpu graph was not pegged, it looked fairly normal. I don't think it was a runaway cron job or anything... it wasn't time for them to run then.

1 participants
0 comments

[FAILURE] XEmacs 21.2-b26 "Millenium" configured for `mips-sgi-irix6.2' 25 years

Paul Bibilo

I cvs updated and: uname -a: IRIX dr2 6.2 03131015 IP22 ../configure '--site-libraries=/usr/local/lib' '--site-includes=/usr/local/include' '--cflags=-g' '--package-path=/devdisk/d54man/gnu/xemacs-beta/packages' '--with-mule=no' XEmacs 21.2-b26 "Millenium" configured for `mips-sgi-irix6.2'. Where should the build process find the source code? /devdisk/d54man/gnu/xemacs-beta/xemacs-21.2 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/irix6-0.h' and `m/iris4d.h' What compiler should XEmacs be built with? cc -g 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? Additional header files: /usr/local/include Additional libraries: /usr/local/lib Runtime library search path: /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 support for X-Face message headers. Compiling in native sound support. Compiling in support for DBM. 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: --------------------------------------------------------- Everything compiled ok, and then at the end of the build process I got the following: Loading /devdisk/d54man/gnu/xemacs-beta/xemacs-21.2/i62-r4k/lisp/fontl-hooks.elc... Loading /devdisk/d54man/gnu/xemacs-beta/xemacs-21.2/i62-r4k/lisp/auto-show.elc... Loading /devdisk/d54man/gnu/xemacs-beta/xemacs-21.2/i62-r4k/lisp/loadhist.elc... Loading /devdisk/d54man/gnu/xemacs-beta/xemacs-21.2/i62-r4k/lisp/loaddefs.elc... Loading site-load... Finding pointers to doc strings... Finding pointers to doc strings...done Dumping under the name xemacs Testing for Lisp shadows ... allocating string (size 16) [] allocating symbol (size 24) [] allocating vector (size 65660) [] allocating string (size 16) [] allocating symbol (size 24) [] allocating string (size 16) [] allocating symbol (size 24) [] allocating string (size 16) [] allocating symbol (size 24) [] allocating string (size 16) [] allocating symbol (size 24) [] make[1]: *** [xemacs] Segmentation fault make[1]: *** Deleting file `xemacs' make[1]: Leaving directory `/devdisk/d54man/gnu/xemacs-beta/xemacs-21.2/i62-r4k/src' make: *** [src] Error 1 Any ideas ? -- Paul

1 participants
0 comments

Re: `yes-or-no-p-dialog-box' crash - Aborts. 25 years

Daniel Pittman

On 01 Jan 2000, Karl M. Hegbloom <karlheg(a)inetarena.com> wrote: > To repeat: Build similar to mine (Installation file attached along > with `ldd' output.) then run `(yes-or-no-p-dialog-box "Yes or No")' > in the *scratch* buffer. When I click on [Yes], [No] or [Cancel], > the button presses, but XEmacs does not respond. When I click the > [X] in the WM frame, it aborts. Here's the stack dump. I get the same behavior from my neXtaw build, including the same abort in lwlib. It looks like, for some reason, Xt believes that the widget passed in is not a subclass of the dialog widget :( On the plus side it does not look like the Xaw detection changes are at fault -- this has the same set of defines for lwlib builds that the old Athena3d code did. Daniel -- People demand freedom of speech to make up for the freedom of thought which they avoid. -- Soren Kierkegaard

2 participants
1 comments

XEmacs 21.2.26 is released. 25 years

Martin Buchholz

I hope you can forgive me for departing from our usual Greek God theme, and naming this beta after the moment we've all been waiting for. Brief summary of changes to 21.2.26 "Millenium" -- Fix unpredictable results, perhaps even crashes, if using the `return from debugger feature' and errors in `eval' or `funcall'. -- fix for Tab widgets causing X errors in XMapWindow(). -------- ChangeLog entries from xemacs-21.2.26/lisp/ChangeLog ------- 1999-12-28 Andy Piper <andy(a)xemacs.org> * wid-edit.el (widget-push-button-value-create): The gui cache does not agree with native widgets which can only be displayed once per window. The reasons for caching are diminished now that we don't hog resources when creating buttons. (widget-push-button-cache) deleted. -------- ChangeLog entries from xemacs-21.2.26/lwlib/ChangeLog ------- 1999-12-29 Andy Piper <andy(a)xemacs.org> * xlwtabs.c (TabsHighlight): use displayChildren for highlighting not num_children. (TabsPage): ditto. -------- ChangeLog entries from xemacs-21.2.26/man/ChangeLog ------- 1999-12-26 Karl M. Hegbloom <karlheg(a)inetarena.com> * internals/internals.texi (garbage_collect_1): Xemacs -> XEmacs -------- ChangeLog entries from xemacs-21.2.26/src/ChangeLog ------- 1999-12-31 Andy Piper <andy(a)xemacs.org> * glyphs-x.c (x_widget_instantiate): Avoid X errors calling XMapWindow() on a NULL pointer X window. 1999-12-31 Martin Buchholz <martin(a)xemacs.org> * data.c (indirect_function): Use signal_void_function_error(). * lisp.h: Modify prototypes for signal_*(). Add SUBR_FUNCTION macro. * eval.c (PRIMITIVE_FUNCALL): Optimize. (signal_void_function_error): return result of Fsignal(). (signal_invalid_function_error): return result of Fsignal(). (signal_wrong_number_of_arguments_error): return result of Fsignal(). (signal_malformed_list_error): Add DOESNT_RETURN. (signal_malformed_property_list_error): Add DOESNT_RETURN. (signal_circular_list_error): Add DOESNT_RETURN. (signal_circular_property_list_error): Add DOESNT_RETURN. (Feval): Use returned results of signal_*(). Avoids a crash! (Ffuncall): Use returned results of signal_*(). Avoids the crash: (setq debug-on-error t) (funcall 'foo) kbd{r42} kbd{RET} - Only check for fun_nargs < subr_min_args if fun_nargs != max_args. (function_argcount): Use signal_invalid_function_error(). (funcall_lambda): Use signal_wrong_number_of_arguments_error(). Use signal_invalid_function_error(). 1999-12-28 Andy Piper <andy(a)xemacs.org> * debug.c: rename debug_loop elements to X_ to avoid name clashes. * menubar-x.c (menu_item_descriptor_to_widget_value_1): strdup string_chars. (menu_item_descriptor_to_widget_value_1): strdup name. (pre_activate_callback): strdup name. * scrollbar-x.c (scrollbar_instance_to_widget_value): strdup name. (x_update_scrollbar_instance_status): use free_widget_value_tree. * dialog-x.c (maybe_run_dbox_text_callback): strdup name. use free_widget_value_tree. (dbox_descriptor_to_widget_value): ditto. * gui-x.c (widget_value_unwind): use free_widget_value_tree. (gui_items_to_widget_values_1): ditto. (gui_items_to_widget_values): ditto. (free_popup_widget_value_tree): free name. 1999-12-27 Andy Piper <andy(a)xemacs.org> * nt.c (fstat): use get_osfhandle rather than the handle directly. From Fabrice Popineau. * process-nt.c (nt_open_network_stream): take types into account when warning. From Fabrice Popineau.

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