October 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Demonstration of XEmacs SIGPIPE misprocessing 25 years, 7 months

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > The silence is deafening. Does this testcase crash anything other than > Linux+GNU uudecode? I use Solaris+GNU uudecode, and I don't get a crash. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- I luv the smell of nature in the morning. Smells like manure!

1 participants
0 comments

Re: Separators on TTY 25 years, 7 months

William M. Perry

SL Baur <steve(a)xemacs.org> writes: > Hrvoje Niksic <hniksic(a)srce.hr> writes in xemacs-beta(a)xemacs.org: > > > SL Baur <steve(a)xemacs.org> writes: > >> Hrvoje Niksic <hniksic(a)srce.hr> writes in xemacs-beta(a)xemacs.org: > >> > >> > When a window is split horizontally (C-x 3) on a TTY, no separator is > >> > drawn. This used to work correctly in 20.4. > >> > >> The divider width is explicitly set to 0. > > > Then this is a bug. It should be 1 on TTY's, not 0. > > I've already dug around the sources to find who made this change. The > closest I can come up with is Kirill (hope he's O.K. and still in Los > Angeles). > > The change made some sense to me because screen real estate is > precious in 80x24, but InfoDock reverted it to 1 some time ago and if > there is no consensus to keeping it the way it is I am amenable to > this change. Please god change it back to 1. It's hideous looking the way it is. :) -Bill P.

1 participants
0 comments

Re: segv in VM, (Poitou, Linux) 25 years, 7 months

Hrvoje Niksic

This is probably redisplay-related. Glynn, have you applied Gunnar's latest patch? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- 4. Thou shalt not warlorde a sig if it bee the sig of Kibo, nor if it bee the sig of the Inner Circle.

2 participants
1 comments

Package vm-1.13: vm.el missing 25 years, 7 months

Heiko Münkel

There is only a vm.elc and no vm.el in vm-1.13-pkg.tar.gz. Is this is a bug? After installation with package-get even the vm.elc is missing in the installed lisp directory .../lib/xemacs/packages/lisp/vm. Heiko

2 participants
3 comments

Re: [Nathan Robertson <cyrus1@ozemail.com.au>] The Site 25 years, 7 months

SL Baur

Marcus Thiessel <marcus(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > ... Should we create some? My suggestion would beto have snapshots > for each major package as Gnus, VM and move that into the package > area. That sounds good. I think a variety of different styles would be best and I don't think they should all come from one person. How would you like to collect them?

2 participants
1 comments

Poitou blanched 25 years, 7 months

Stephen J. Turnbull

All of a sudden (CVS update to "Poitou") my text window backgrounds are white instead of grey, although {menu,tool,status,scroll}bars are all grey. This doesn't happen under -vanilla, so it must be something in my customizations that has changed effect. However, I don't seem to have any customizations that explicitly set backgrounds. Is this intentional? Also, some positive feedback: suddenly XEmacs is picking a different kanji font and/or size. This is temporarily annoying to me (it's ugly), but I think probably somebody made a patch for the better. The kanji font XEmacs is picking now is better matched (IMO, and for two fonts and two sizes I tried) to the ISO-8859-1 fonts then the former selection, because it is always smaller. I used to often see kanji fonts that were too large in the sense that they would get clipped, particularly in the status bar. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +1 (298) 53-5091

3 participants
11 comments

[Crash] VM 6.61 and 21.0 "Norwegian" 25 years, 7 months

Marcus Thiessel

This crash hit me when I tried to save&quit from VM via menu. --[[text/plain]] Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. 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/src/xemacs-21.0/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: # (condition-case ... . error) # (catch top-level ...) --[[text/plain]] gdb /opt/src/xemacs-21.0/src/xemacs core Wildebeest is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for Wildebeest; type "show warranty" for details. Hewlett-Packard Wildebeest 0.75.02 (based on GDB 4.16) (built for PA-RISC 1.1 or 2.0(narrow), HP-UX 11.00) Copyright 1996, 1997 Free Software Foundation, Inc... Core was generated by `xemacs'. Program terminated with signal 11, Segmentation fault. warning: The shared libraries were not privately mapped; setting a breakpoint in a shared library will not work until you rerun the program. Reading symbols from /usr/lib/Motif1.2_R6/libXm.3...done. Reading symbols from /usr/lib/libcanna.sl...done. Reading symbols from /usr/lib/libRKC.sl...done. Reading symbols from /usr/dt/lib/libDtSvc.3...done. Reading symbols from /usr/lib/libXm.4...done. Reading symbols from /usr/lib/libXp.2...done. Reading symbols from /usr/dt/lib/libtt.3...done. Reading symbols from /usr/lib/libnsl.1...done. Reading symbols from /usr/lib/libxti.2...done. Reading symbols from /usr/lib/X11R6/libXt.3...done. Reading symbols from /usr/lib/X11R6/libXext.3...done. Reading symbols from /usr/lib/X11R6/libX11.3...done. Reading symbols from /usr/lib/X11R6/libSM.2...done. Reading symbols from /usr/lib/X11R6/libICE.2...done. Reading symbols from /usr/lib/libm.2...done. Reading symbols from /usr/lib/libc.2...done. Reading symbols from /usr/lib/libdld.2...done. Reading symbols from /usr/lib/libnss_dns.1...done. Reading symbols from /usr/lib/libnss_nis.1...done. Reading symbols from /usr/lib/libnss_files.1...done. #0 0xc00f0a10 in kill () from /usr/lib/libc.2 #0 0xc00f0a10 in kill () from /usr/lib/libc.2 (gdb) where #0 0xc00f0a10 in kill () from /usr/lib/libc.2 #1 0x9912c in fatal_error_signal () #2 <signal handler called> #3 0xb2c20 in Fcharacter_to_event () #4 0x178df8 in event_matches_key_specifier_p () #5 0x109094 in command_builder_operate_menu_accelerator () #6 0x10ee38 in 2a5_1ffb_cl_command_builder_find_leaf () #7 0x10d960 in fd_1ffb_cl_lookup_command_event () #8 0x10b1c4 in Fdispatch_event () #9 0x75318 in command_loop_1 () #10 0xa1320 in condition_case_1 () #11 0x7489c in command_loop_2 () #12 0xa0e10 in internal_catch () #13 0x74ab4 in initial_command_loop () #14 0x99f6c in xemacs_21_0_hppa1_1_hp_hpux11_00 () #15 0xb9b44 in run_time_remap () #16 0x9b890 in main ()

1 participants
0 comments

Re: Kanji font selection (Mule showstopper?) 25 years, 7 months

SL Baur

Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes in xemacs-beta(a)xemacs.org: ... > The issue is that on my system, at least, any attempt to alter _any_ > faces, font or size of any charset, via the Options menu results in > completely unusable kanji fonts. These cannot be changed _at all_ > outside of Lisp AFAIK, short of restarting XEmacs. > That is not acceptable to ordinary users, and thus a showstopper IMO. > Don't release a Mule XEmacs in this state, please. Ben's away for a week and a half from today. There will not be any 21.0 release without his O.K.

1 participants
0 comments

Re: Success 21.2-mumble on AIX 4.3.1 25 years, 7 months

SL Baur

Valdis Kletnieks <Valdis.Kletnieks(a)vt.edu> writes in xemacs-beta(a)xemacs.org: > The announcement on Sep 29 said '21.2-pre7', but the tarball on > ftp.xemacs.org is labelled 21.2-b2. There was a 21.2-pre7 announced on Sept. 27. As per the above, always prefer a later time-stamped tarball.

1 participants
0 comments

Re: Proposed version number change for 21.2 25 years, 7 months

Didier Verna

SL Baur <steve(a)xemacs.org> writes: > I am undecided whether the string `beta' should remain in the version > string. This proposal is biased towards the side of minimal change. I vote for keeping it. It will prevent any ambiguity especially for people who are not on the list and grab a release from time to time. Also, the new naming policy should be clearly detailed somewhere. I think it should go on the web site for instance. --didier

1 participants
0 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 October 1998