January 2000 - XEmacs-Beta - XEmacs Mailing List Archives

RE: New packages and tarballs uploaded 24 years, 10 months

Damon Lipparelli

Andreas, The new version of texinfo (1.18) isn't there. Thanks, -lipp -----Original Message----- From: Andreas Jaeger [mailto:aj＠xemacs.org] Sent: Monday, January 24, 2000 2:49 AM To: xemacs-announce(a)xemacs.org Subject: New packages and tarballs uploaded I've uploaded new packages and tarballs to ftp.xemacs.org:/pub/xemacs/packages. What's new? - texinfo: Synch with FSF 20.5 - xemacs-base: Fixes for passwd and comint - mail-lib: Synch of mail-utils with FSF 20.5. - progmodes: autoconf and python modes updated - edit-utils: Fix bookmark.el - auctec: Version 9.9p Here're file sizes and package names: 132921 Jan 21 03:38 texinfo-1.18-pkg.tar.gz 375623 Jan 19 11:35 auctex-1.19-pkg.tar.gz 440635 Jan 21 03:40 xemacs-base-1.37-pkg.tar.gz 580217 Jan 19 11:36 edit-utils-1.45-pkg.tar.gz 603792 Jan 19 11:38 prog-modes-1.23-pkg.tar.gz 147112 Jan 22 04:36 mail-lib-1.28-pkg.tar.gz 4331958 Jan 24 05:38 xemacs-mule-sumo-2000-01-24.tar.gz 34 Jan 24 05:40 xemacs-mule-sumo.tar.gz -> xemacs-mule-sumo-2000-01-24.tar.gz 16284226 Jan 24 05:46 xemacs-sumo-2000-01-24.tar.gz 29 Jan 24 05:46 xemacs-sumo.tar.gz -> xemacs-sumo-2000-01-24.tar.gz Andreas P.S. And here're the assorted ChangeLogs since the package release from 2000-01-15: ChangeLog for prog-modes: 2000-01-19 Akim Demaille <akim(a)epita.fr> * autoconf-mode.el (autoconf-font-lock-keywords): Support `A._DEFUN' definitions: Autoconf now uses AC_DEFUN, AU_DEFUN, AH_DEFUN, and others are to come. 2000-01-19 Andreas Jaeger <aj(a)suse.de> * python-mode.el: Version 3.105 from Barry Warsaw. ChangeLog for edit-utils: 2000-01-19 Adrian Aichner <aichner(a)ecf.teradyne.com> * bookmark.el (bookmark-completing-read): Use new argument default of `completing-read'. Drop last argument if we get signaled `wrong-number-of-arguments'. Document the change. Re-indent function. ChangeLog for auctex: 2000-01-19 Andreas Jaeger <aj(a)suse.de> * Updated with AUC TeX 9.9p. For texinfo: 2000-01-19 Yoshiki Hayashi <yoshiki(a)xemacs.org> * informat.el: (Info-validate-error-buffer): New variable. Change buffer name. (Info-validate-node-name): Fix Ebola. (Info-file-data): Use non directory part of a file name. (Info-validate): Add two lines of output to make parsing function happy. 1999-12-09 Yoshiki Hayashi <t90553(a)mail.ecc.u-tokyo.ac.jp> * texinfmt.el: Synched with FSF 20.5. * informat.el: Synched with FSF 20.5. 2000-01-13 Yoshiki Hayashi <t90553(a)mail.ecc.u-tokyo.ac.jp> * texinfo.el (texinfo-environment-regexp): Add vtable. For xemacs-base: 2000-01-19 Yoshiki Hayashi <yoshiki(a)xemacs.org> * passwd.el (passwd-insecure-display): Remove face property set by passwd-secure-display. 2000-01-18 Martin Buchholz <martin(a)xemacs.org> * comint.el (comint-mode): Add autoload cookie. For mail-lib: 2000-01-05 Yoshiki Hayashi <t90553(a)mail.ecc.u-tokyo.ac.jp> * mail-utils.el: Synch with FSF 20.5. -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.rhein-neckar.de

1 participants
0 comments

Glyph test crashes XEmacs 24 years, 10 months

Yoshiki Hayashi

Evaluating following test in glyph-test.el crashes XEmacs. (set-extent-begin-glyph (make-extent (point) (point)) (make-glyph [button :face modeline-mousable :descriptor "ok" :callback foo :image [xpm :file "../etc/xemacs-icon.xpm"]])) Lisp backtrace and C stacktrace follows: ./src/xemacs -vanilla 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 /src/xemacs/src/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: # (unwind-protect ...) # (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque_ptr, adr=0x829ecac) 0x82f40c0> ...) # (unwind-protect ...) # (unwind-protect ...) # bind (inhibit-quit) # (condition-case ... . error) # (catch top-level ...) Segmentation fault (core dumped) (gdb) where #0 0x4039e621 in kill () from /lib/libc.so.6 #1 0x808e7e4 in fatal_error_signal (sig=11) at emacs.c:278 #2 0x4039e558 in sigaction () from /lib/libc.so.6 #3 0x8114716 in instantiate_image_instantiator (device=138027248, domain=140054736, instantiator=142320608, pointer_fg=137122684, pointer_bg=137122684, dest_mask=239, glyph=140416248) at glyphs.c:606 #4 0x8119164 in image_instantiate (specifier=140474320, matchspec=136889516, domain=140054736, instantiator=142320608, depth=3) at glyphs.c:2762 #5 0x8091b39 in call_with_suspended_errors_1 (opaque_arg=137327736) at eval.c:2046 #6 0x8091e51 in call_with_suspended_errors ( fun=0x8118b48 <image_instantiate>, retval=136889516, class=137243996, errb={ really_unlikely_name_to_have_accidentally_in_a_non_errb_structure = 42}, nargs=5) at eval.c:1304 #7 0x818ca22 in specifier_instance_from_inst_list (specifier=140474320, matchspec=136889516, domain=140054736, inst_list=141610880, errb={ really_unlikely_name_to_have_accidentally_in_a_non_errb_structure = 42}, no_quit=1, depth=3) at specifier.c:2450 #8 0x818cde5 in specifier_instance (specifier=140474320, matchspec=136889516, domain=140054736, errb={ really_unlikely_name_to_have_accidentally_in_a_non_errb_structure = 42}, no_quit=1, no_fallback=0, depth=1) at specifier.c:2565 ---Type <return> to continue, or q <return> to quit--- #9 0x811a449 in glyph_width (glyph_or_image=140416248, domain=140054736) at glyphs.c:3503 #10 0x815ecd3 in add_glyph_rune (data=0xbffff400, gb=0x8616e48, pos_type=0, allow_cursor=0, cachel=0x0) at redisplay.c:1544 #11 0x815fe2a in create_text_block (w=0x85910d0, dl=0x87b04f0, bi_start_pos=386, prop=0xbffff550, type=1) at redisplay.c:1758 #12 0x815d249 in generate_display_line (w=0x85910d0, dl=0x87b04f0, bounds=1, start_pos=386, prop=0xbffff550, type=1) at redisplay.c:730 #13 0x81660b1 in regenerate_window (w=0x85910d0, start_pos=386, point=667, type=1) at redisplay.c:5171 #14 0x81679ad in redisplay_window (window=140054736, skip_selected=0) at redisplay.c:6120 #15 0x81680b8 in redisplay_frame (f=0x8590fa0, preemption_check=0) at redisplay.c:6393 #16 0x8168290 in redisplay_device (d=0x83a20f0) at redisplay.c:6460 #17 0x8168629 in redisplay_without_hooks () at redisplay.c:6549 #18 0x816f272 in redisplay () at redisplay.c:6606 #19 0x80d8c6e in Fnext_event (event=142693548, prompt=137122684) at event-stream.c:2237 #20 0x80728d1 in Fcommand_loop_1 () at cmdloop.c:566 #21 0x8072b7d in command_loop_1 (dummy=137122684) at cmdloop.c:490 #22 0x8090bb2 in condition_case_1 (handlers=137122780, bfun=0x8072b34 <command_loop_1>, barg=137122684, ---Type <return> to continue, or q <return> to quit--- hfun=0x8072bec <cmd_error>, harg=137122684) at eval.c:1629 #23 0x8072cdf in command_loop_2 (dummy=137122684) at cmdloop.c:252 #24 0x8097d0c in internal_catch (tag=137196900, func=0x8072ca0 <command_loop_2>, arg=137122684, threw=0x0) at eval.c:1304 #25 0x80720fb in initial_command_loop (load_me=137122684) at cmdloop.c:301 #26 0x808c9ee in xemacs_21_2_b27_i686_pc_linux () at emacs.c:1906 #27 0x808ea00 in voodoo_free_hook (mem=0x2) at emacs.c:2331 #28 0x403987e2 in __libc_start_main () from /lib/libc.so.6 uname -a: Linux buck 2.2.13 #9 Thu Dec 23 11:11:36 JST 1999 i686 unknown ./configure '--prefix=/opt/local' '--with-mule' '--cflags=-g -O3 -Wall -Wno-switch -fno-gcse' XEmacs 21.2-b27 "Hera" 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 -fno-gcse 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 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 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

2 participants
3 comments

Re: /etc/ld.so.conf handling doesn't work for me 24 years, 10 months

Neal D. Becker

The runtime linker has a way to tell if the libs are for libc5 or libc6. ld doesn't have that info. I think this whole concept is doomed to failure. I think you have to make sure you're not mixing libc5 and libc6 libraries in the ld command.

1 participants
0 comments

Re: /etc/ld.so.conf handling doesn't work for me 24 years, 10 months

Jan Vroonhof

Daniel Pittman <daniel(a)danann.net> writes: > I tried to come up with a good configure-time test but don't know X much > at all, yet. Not to write a new application for configure to test, > anyway.[1] Why do you need an X app? Won't something like #include bla. typedef .... funcpointer; /* Pull in Xaw in link &/ funcpointer dummy = PlainXaW function; int main(int argc, char *argv[]) { /* do dlopen thingy */ return AthenaIs3D ? EXIT_FAILURE : EXIT_SUCESS } The trickiest part to me seems embedding it into configure correctly. Jan

1 participants
0 comments

Duplicated articles. 24 years, 10 months

Nick V. Pakoulin

Is it a Gnus feature (v5.6.45) or xemacs-beta make duplicates? By the way, xemacs-patches makes the same. ----------------------------------------------------------------

1 participants
0 comments

Re: /etc/ld.so.conf handling doesn't work for me 24 years, 10 months

Daniel Pittman

On 24 Jan 2000, Andreas Jaeger <aj(a)suse.de> wrote: >>>>>> Martin Buchholz writes: > > mb> Unless someone can come up with a suggestion, I will reverse the > mb> /etc/ld.so.conf patch. Andreas, this is actually your specialty. > mb> What do you propose? > > Revert the /etc/ld.so.conf patch and do some runtime checking (AFAIK > this has been already proposed by somebody else). Done. Jan requested an additional #ifdef DLOPEN in there, I can send that as a patch now. I tried to come up with a good configure-time test but don't know X much at all, yet. Not to write a new application for configure to test, anyway.[1] I think that the runtime test is sufficient though. Daniel Footnotes: [1] If anyone has some pointers to `A complete idiots guide to X', please pass 'em on. Something starting at main(), preferably. -- When your hammer is C++, everything begins to look like a thumb. -- Simon Brooke

1 participants
0 comments

New packages and tarballs uploaded 24 years, 10 months

Andreas Jaeger

I've uploaded new packages and tarballs to ftp.xemacs.org:/pub/xemacs/packages. What's new? - texinfo: Synch with FSF 20.5 - xemacs-base: Fixes for passwd and comint - mail-lib: Synch of mail-utils with FSF 20.5. - progmodes: autoconf and python modes updated - edit-utils: Fix bookmark.el - auctec: Version 9.9p Here're file sizes and package names: 132921 Jan 21 03:38 texinfo-1.18-pkg.tar.gz 375623 Jan 19 11:35 auctex-1.19-pkg.tar.gz 440635 Jan 21 03:40 xemacs-base-1.37-pkg.tar.gz 580217 Jan 19 11:36 edit-utils-1.45-pkg.tar.gz 603792 Jan 19 11:38 prog-modes-1.23-pkg.tar.gz 147112 Jan 22 04:36 mail-lib-1.28-pkg.tar.gz 4331958 Jan 24 05:38 xemacs-mule-sumo-2000-01-24.tar.gz 34 Jan 24 05:40 xemacs-mule-sumo.tar.gz -> xemacs-mule-sumo-2000-01-24.tar.gz 16284226 Jan 24 05:46 xemacs-sumo-2000-01-24.tar.gz 29 Jan 24 05:46 xemacs-sumo.tar.gz -> xemacs-sumo-2000-01-24.tar.gz Andreas P.S. And here're the assorted ChangeLogs since the package release from 2000-01-15: ChangeLog for prog-modes: 2000-01-19 Akim Demaille <akim(a)epita.fr> * autoconf-mode.el (autoconf-font-lock-keywords): Support `A._DEFUN' definitions: Autoconf now uses AC_DEFUN, AU_DEFUN, AH_DEFUN, and others are to come. 2000-01-19 Andreas Jaeger <aj(a)suse.de> * python-mode.el: Version 3.105 from Barry Warsaw. ChangeLog for edit-utils: 2000-01-19 Adrian Aichner <aichner(a)ecf.teradyne.com> * bookmark.el (bookmark-completing-read): Use new argument default of `completing-read'. Drop last argument if we get signaled `wrong-number-of-arguments'. Document the change. Re-indent function. ChangeLog for auctex: 2000-01-19 Andreas Jaeger <aj(a)suse.de> * Updated with AUC TeX 9.9p. For texinfo: 2000-01-19 Yoshiki Hayashi <yoshiki(a)xemacs.org> * informat.el: (Info-validate-error-buffer): New variable. Change buffer name. (Info-validate-node-name): Fix Ebola. (Info-file-data): Use non directory part of a file name. (Info-validate): Add two lines of output to make parsing function happy. 1999-12-09 Yoshiki Hayashi <t90553(a)mail.ecc.u-tokyo.ac.jp> * texinfmt.el: Synched with FSF 20.5. * informat.el: Synched with FSF 20.5. 2000-01-13 Yoshiki Hayashi <t90553(a)mail.ecc.u-tokyo.ac.jp> * texinfo.el (texinfo-environment-regexp): Add vtable. For xemacs-base: 2000-01-19 Yoshiki Hayashi <yoshiki(a)xemacs.org> * passwd.el (passwd-insecure-display): Remove face property set by passwd-secure-display. 2000-01-18 Martin Buchholz <martin(a)xemacs.org> * comint.el (comint-mode): Add autoload cookie. For mail-lib: 2000-01-05 Yoshiki Hayashi <t90553(a)mail.ecc.u-tokyo.ac.jp> * mail-utils.el: Synch with FSF 20.5. -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.rhein-neckar.de

1 participants
0 comments

Re: /etc/ld.so.conf handling doesn't work for me 24 years, 10 months

Andreas Jaeger

>>>>> Martin Buchholz writes: mb> Unless someone can come up with a suggestion, I will reverse the mb> /etc/ld.so.conf patch. Andreas, this is actually your specialty. mb> What do you propose? Revert the /etc/ld.so.conf patch and do some runtime checking (AFAIK this has been already proposed by somebody else). Andreas -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.rhein-neckar.de

1 participants
0 comments

Re: [PATCH] Use system underline and struck thru fonts 24 years, 10 months

William M. Perry

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > >>>>> "-BP" == William M Perry <wmperry(a)aventail.com> writes: > > >> No, it's not possible. There are four problems: > > >> (1) The face properties may overspecify the font on any given > >> system (eg, color on a mono system, family on a TTY); in such a > >> case the face system will have to choose a compromise font. > >> The user should be able to override this arbitrary choice > >> directly. > > >> (2) The face properties may underspecify the font, in which > >> case the face system makes an arbitrary choice. Again, the > >> user should be able to override. > > -BP> Neither of these should ever happen with proper property > -BP> merging. The default font would ALWAYS be fully specified. > -BP> Either by the user or by a combination of the user and > -BP> window-system-specific defaults. > > I don't understand. Of course the default font would always be > exactly specified, and so would every font actually used to display > text. I meant that with a fully specified font, there would be no 'arbitrary' choices involved. Although some things from the default face wouldn't necessarily make sense if you've changed charsets, etc. Hrm. > My point is that our face model cannot possibly account for all font > properties, e.g. those in use by future intergalactic alien allies, and > therefore although the face system would resolve both under- and > over-determined specs, the user might not like the outcome. (The main > problem is that the maintainer of the font handler in question might not > be able or willing to change the abstract face system, _especially if it > involves an API or face model change_.) This is why I put in the font-maximum-slippage, and planned on adding more before I decided it was wasted effort to try and do this in lisp. There should definitely be appropriate variables to control the selection, including the '#%!＠ you always use my default face' that Emacs/W3 allows you to do now. > If so, the user could specify the font explicitly, but that's not very > friendly or general. We should provide direct access via Lisp to > underlying font models, however ugly, and not force the user to fully > specify the font. Surely _Custom_ should avoid using those whenever > possible, and maybe even override or redirect user attempts to use font > properties when a corresponding face property is available. Isn't a lot of this taken care of by the charset hints right now? I'm tired and getting a bit lost, so forgive me if I misremember. :) -Bill P.

2 participants
1 comments

Arguments to macros 24 years, 10 months

Hrvoje Niksic

Why is macro arglist not displayed with `C-h f'? Case in point: I'm interested in `check-argument-type' macro. I press `C-h f check-argument-type RET', and I get: `check-argument-type' is a compiled Lisp macro -- loaded from "/home/hniksic/work/emacs/build/lisp/subr.elc" Documentation: Check that ARGUMENT satisfies PREDICATE. ... Arglist is not printed anywhere, so this might imply that ARGUMENT comes before PREDICATE, while in fact it doesn't. So I wonder: why are arglists not printed for macros? Can we fix that?

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