May 1999 - XEmacs-Beta - XEmacs Mailing List Archives

21.2 font menu for mswindows 20 years, 8 months

Andy Piper

As always I have split out the generic parts. This also includes the expand-file-name usage changes suggested by Hrvoje. I will apply this to cvs. andy 1999-05-30 Andy Piper <andy(a)xemacs.org> * msw-faces.el (mswindows-font-regexp): new font matching regexp for use by the font menu. * msw-font-menu.el: new file implementing mswindows specific font-menu behaviour. (mswindows-font-menu-registry-encoding): new function mirroring x version. (mswindows-font-menu-junk-families): ditto. (hack-font-truename): ditto. (mswindows-font-regexp-ascii): ditto. (mswindows-reset-device-font-menus): ditto. (mswindows-font-menu-font-data): ditto. (mswindows-font-menu-load-font): ditto. * x-font-menu.el (x-reset-device-font-menus): made device specific. (x-font-menu-font-data): ditto. (x-font-menu-load-font): ditto. * font-menu.el: new file implementing generic font menu behaviour. (font-menu-ignore-scaled-fonts): copied from x-font-menu.el and made device independent. (font-menu-this-frame-only-p): ditto. (font-menu-preferred-resolution): ditto. (font-menu-size-scaling): new variable used to determine whether sizes are in points or tenths of a point. (vassoc): moved from x-font-menu.el. (device-fonts-cache): ditto. (device-fonts-cache): ditto. (flush-device-fonts-cache): ditto. (reset-device-font-menus): copied from x-font-menu.el and made device independent. Most functionality deferred to device-dependent versions. (font-menu-family-constructor): copied from x-font-menu.el and made device independent. (font-menu-size-constructor): ditto. (font-menu-weight-constructor): ditto. (font-menu-set-font): ditto. (font-menu-change-face): ditto. (font-menu-load-font): new device method. (font-menu-font-data): ditto. * x-font-menu.el: The above functions deleted. 1999-05-26 Andy Piper <andy(a)xemacs.org> * update-elc.el: * make-docfile.el: * loadup.el: rehash expand-file-name usage to not use default-directory.

1 participants
0 comments

Re: [Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>] more on the emacs-20.3 segfault 20 years, 8 months

Jan Vroonhof

Andreas Jaeger <aj(a)arthur.rhein-neckar.de> writes: > I thought the following might be of interest to you. We (glibc > developers) received a bug report about emacs-20.3 with glibc 2.1.1. > I can't reproduce this with XEmacs 21.0p2. That's probably 21.1p2. The reason you don't see it is that on glibc2.x systems XEmacs uses the system malloc instead of its own doug lea allocator. The main reason for this is that we don't run into obscure and hard to debug problems like this. > Nevertheless the patch looks fine (I'm just running a mule-enabled > XEmacs 21.0p2 with it) and should work with glibc 2.0 and 2.1 (I only > tested with glibc 2.1.1). >From glancing at the patch in its current incarnation, it seems awfully glibc specific to me. If I understand it correctly. It works because the glibc startup code works by calling this hook somewhere. Who says the Solaris startup code will do that? Jan P.S. Why does Glibc 2.1.x define I_SETSIG ? -- Jan Vroonhof http://www.math.ethz.ch/~vroonhof/ Mathematik, vroonhof ＠ math.ethz.ch HG E16, ETH-Zentrum, Tel: +41-1-6325456/25154 Raemistrasse 101, CH-8092 Zuerich. Fax: +41-1-6321085

1 participants
0 comments

Re: [Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>] more on the emacs-20.3 segfault 20 years, 8 months

Adrian Aichner

>>>>> "Andreas" == Andreas Jaeger <aj(a)arthur.rhein-neckar.de> writes: >>>>> "Andreas" == Andreas Jaeger <aj(a)arthur.rhein-neckar.de> writes: Andreas> Hi Xemacs-Patchers, Andreas> I thought the following might be of interest to you. We Andreas> (glibc developers) received a bug report about emacs-20.3 Andreas> with glibc 2.1.1. I can't reproduce this with XEmacs Andreas> 21.0p2. Andreas> Adrian > Hello Andreas, Andreas> Adrian > Andreas> Adrian > I am not aware of such a version. Andreas> Adrian > emacs-version "21.1 \"20 Minutes to Nikko\" XEmacs Lucid (beta2)" Andreas> Adrian > is the closest I can guess. Andreas> I'm using XEmacs 21.1-p2 "20 Minutes to Nikko" (according Andreas> to M-x describe-installation) --- and according to my Andreas> User-Agent line which you could have checked ;-). But I Andreas> don't think this is really relevant here. Would my checking of your User-Agent line make 21.0p2 come into existence all of a sudden? Adrian -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Re: [Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>] more on the emacs-20.3 segfault 20 years, 8 months

Andreas Jaeger

>>>>> "Andreas" == Andreas Jaeger <aj(a)arthur.rhein-neckar.de> writes: Andreas> Hi Xemacs-Patchers, Andreas> I thought the following might be of interest to you. We Andreas> (glibc developers) received a bug report about emacs-20.3 Andreas> with glibc 2.1.1. I can't reproduce this with XEmacs Andreas> 21.0p2. Adrian > Hello Andreas, Adrian > Adrian > I am not aware of such a version. Adrian > emacs-version "21.1 \"20 Minutes to Nikko\" XEmacs Lucid (beta2)" Adrian > is the closest I can guess. I'm using XEmacs 21.1-p2 "20 Minutes to Nikko" (according to M-x describe-installation) --- and according to my User-Agent line which you could have checked ;-). But I don't think this is really relevant here. I did send the patch for discussion and further testing and thought the information in it might become relevant. Looking at Wolfram's analysis of the situation, XEmacs should segfault the same way as FSF-Emacs does --- but AFAIK it doesn't. Either the analysis is wrong, we're just lucky with XEmacs or XEmacs is just better;-). Andreas -- Andreas Jaeger aj(a)arthur.rhein-neckar.de jaeger(a)informatik.uni-kl.de for pgp-key finger ajaeger(a)aixd1.rhrk.uni-kl.de

1 participants
0 comments

core dump in XtDestroyWidget() on HPUX 10.20 20 years, 8 months

David S. Miller

core dump in XtDestroyWidget() on HPUX 10.20 I have seen XEmacs core dump while taking dialog boxes down. Specifically, when a dialog box is completed with a manual entry and a carraige return, such as File => Save As... type the name and press enter. This does not seem to happen when mouse selecting OK. It doesn't always happen on the first try, but I can reliably reproduce this by the third or fourt try. I'll try to include all relaveent information. I have reproduced this error on the following versions 20.4, 21.0.67, and 21.1.2. The included data is from 21.1.2. Version 20.2 DOES NOT express the error. What else should be included to make this report complete? dsm(a)fc.hp.com Xemacs version 21.1.2 expresses a core dump under the following conditions: HPUX 10.20 in Japanese SJIS mode $LANG=ja_JP.SJIS +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ configure options +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ./configure hppa1.1-hp-hpux10.20 \ --extra-verbose \ --compiler="/opt/ansic/bin/cc" \ --x-includes="/usr/include/X11R6 -I/usr/include/Motif1.2_R6" \ --x-libraries="/usr/lib/X11R6 -L/usr/lib/Motif1.2_R6" \ --error-checking=none \ --dynamic=no \ --with-x11=yes \ --with-menubars=lucid \ --with-scrollbars=motif \ --with-dialogs=motif \ --with-xmu=no \ --with-xim \ --with-mule=yes \ --with-cde=yes \ --debug \ --cflags="+DA1.1 +DD32 +O2 +Onolimit +Odataprefetch +Ovectorize +Ofastaccess +Oprocelim" ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .emacs contents ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ (set-language-environment 'Japanese) (set-pathname-coding-system 'shift_jis-unix) (set-default-buffer-file-coding-system 'shift_jis) (set-buffer-file-coding-system-for-read 'shift_jis) (set-keyboard-coding-system 'shift_jis) (set-terminal-coding-system 'shift_jis) (set-default-coding-systems 'shift_jis) ;; I can reproduce the core with NO .emacs file ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ core dump runtime output (machine named hellcat) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ hellcat, (10:27)> ./xemacs 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 /home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-21.1.2/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: kill-emacs() # bind (arg) save-buffers-kill-emacs(nil) # bind (command-debug-status) call-interactively(save-buffers-kill-emacs) # (condition-case ... . error) # (catch top-level ...) Memory fault(coredump) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ gdb backtrace ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ hellcat, (10:42)> /nfs/zappa/usr/local/bin/gdb /home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-21.1.2/src/xemacs core GNU gdb 4.17 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "hppa1.1-hp-hpux10.20"...(no debugging symbols found)... 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 ./xemacs...(no debugging symbols found)...done. Reading symbols from /usr/dt/lib/libXm.1...(no debugging symbols found)...done. Reading symbols from /usr/dt/lib/libDtSvc.1...(no debugging symbols found)...done. Reading symbols from /usr/dt/lib/libtt.1...(no debugging symbols found)...done. Reading symbols from /usr/dt/lib/libXt.1...(no debugging symbols found)...done. Reading symbols from /usr/lib/X11R6/libXext.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/X11R6/libX11.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/X11R6/libSM.1...(no debugging symbols found)...done. Reading symbols from /usr/lib/X11R6/libICE.1...(no debugging symbols found)...done. Reading symbols from /usr/lib/libc.1...(no debugging symbols found)...done. Reading symbols from /usr/lib/libdld.sl...(no debugging symbols found)...done. Reading symbols from /usr/lib/nls/loc/locales.1//ja_JP.SJIS...(no debugging symbols found)...done. Reading symbols from /usr/lib/nls/loc/methods/libSJIS.sl...(no debugging symbols found)...done. #0 0xc0137598 in kill () (gdb) where #0 0xc0137598 in kill () #1 0x85850 in fatal_error_signal () #2 <signal handler called> #3 0xc177da00 in _XimProtoKeypressFilter () #4 0xc177db24 in _XimFilterKeypress () #5 0xc174db58 in XFilterEvent () #6 0xc13248b4 in DispatchEvent () #7 0xc132553c in DecideToDispatch () #8 0xc1325624 in XtDispatchEvent () #9 0xc14bc5c4 in RemoveAllPMgr () #10 0xc13190fc in XtCallCallbackList () #11 0xc1320dd0 in Phase2Callbacks () #12 0xc1320d3c in Recursive () #13 0xc132113c in XtPhase2Destroy () #14 0xc1321300 in _XtDoPhase2Destroy () #15 0xc1321484 in XtDestroyWidget () #16 0x172d7c in x_delete_frame () #17 0xf3524 in delete_frame_internal () #18 0x78768 in delete_device_internal () #19 0x7035c in delete_console_internal () #20 0x87bc4 in Fkill_emacs () #21 0x8de24 in funcall_recording_as () #22 0x8e170 in Ffuncall () #23 0x64580 in $0000004D () Cannot access memory at address 0x0. (gdb) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ $LANG +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ hellcat, (10:45)> echo $LANG ja_JP.SJIS +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Stack trace from 20.4 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ #0 0xc0137598 in kill () from /usr/lib/libc.1 #1 0x64d3c in fatal_error_signal () from /tmp_mnt/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-20.4/src/./xem acs #2 <signal handler called> #3 0xc177d850 in _XimOnKeysCheck () from /usr/lib/X11R6/libX11.2 #4 0xc177da40 in _XimProtoKeypressFilter () from /usr/lib/X11R6/libX11.2 #5 0xc177db24 in _XimFilterKeypress () from /usr/lib/X11R6/libX11.2 #6 0xc174db58 in XFilterEvent () from /usr/lib/X11R6/libX11.2 #7 0xc12e48b4 in DispatchEvent () from /usr/dt/lib/libXt.1 #8 0xc12e553c in DecideToDispatch () from /usr/dt/lib/libXt.1 #9 0xc12e5624 in XtDispatchEvent () from /usr/dt/lib/libXt.1 #10 0xc147c5c4 in RemoveAllPMgr () from /usr/dt/lib/libXm.1 #11 0xc12d90fc in XtCallCallbackList () from /usr/dt/lib/libXt.1 #12 0xc12e0dd0 in Phase2Callbacks () from /usr/dt/lib/libXt.1 #13 0xc12e0d3c in Recursive () from /usr/dt/lib/libXt.1 #14 0xc12e113c in XtPhase2Destroy () from /usr/dt/lib/libXt.1 #15 0xc12e1300 in _XtDoPhase2Destroy () from /usr/dt/lib/libXt.1 #16 0xc12e1484 in XtDestroyWidget () from /usr/dt/lib/libXt.1 #17 0x158a80 in x_delete_frame () from /tmp_mnt/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-20.4/src/./xem acs #18 0xd7a20 in delete_frame_internal () #19 0xd7b30 in Fdelete_frame () from /tmp_mnt/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-20.4/src/./xem acs #20 0x6cd14 in funcall_recording_as () from /tmp_mnt/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-20.4/src/./xem acs #21 0x6d358 in Ffuncall () from /tmp_mnt/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-20.4/src/./xem acs #22 0x3fb20 in Fbyte_code () from /tmp_mnt/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-20.4/src/./xem acs #23 <function called from gdb>

3 participants
3 comments

Re: [Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>] more on the emacs-20.3 segfault 20 years, 8 months

Adrian Aichner

>>>>> "Andreas" == Andreas Jaeger <aj(a)arthur.rhein-neckar.de> writes: Andreas> Hi Xemacs-Patchers, Andreas> I thought the following might be of interest to you. We Andreas> (glibc developers) received a bug report about emacs-20.3 Andreas> with glibc 2.1.1. I can't reproduce this with XEmacs Andreas> 21.0p2. Hello Andreas, I am not aware of such a version. emacs-version "21.1 \"20 Minutes to Nikko\" XEmacs Lucid (beta2)" is the closest I can guess. Regards, Adrian Andreas> Nevertheless the patch looks fine (I'm just running a Andreas> mule-enabled XEmacs 21.0p2 with it) and should work with Andreas> glibc 2.0 and 2.1 (I only tested with glibc 2.1.1). Andreas> Andreas Andreas> From: Wolfram Gloger <wmglo(a)dent.med.uni-muenchen.de> Andreas> Subject: more on the emacs-20.3 segfault Andreas> Date: Fri May 28 22:03:33 1999 -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Configure failure 20 years, 8 months

Charles G Waldman

I updated two things at the same time and I don't know which one is to blame. I updated my copy of the 21.1 sources from CVS. I also have a brand-new glibc, built from the 2.1.1 glibc sources. Now when I try to configure XEmacs I get: buffalo:xemacs-21$ ./configure checking host system type... checking whether ln -s works... yes checking the configuration name Configuration name missing. Usage: /usr/local/src/xemacs-21/config.sub CPU-MFR-OPSYS or /usr/local/src/xemacs-21/config.sub ALIAS where ALIAS is a recognized configuration type. All that I get in config.log is this: This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. configure:747: checking host system type configure:761: checking whether ln -s works configure:998: checking the configuration name Any suggestions? Thanks in advance.

1 participants
1 comments

[Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>] more on the emacs-20.3 segfault 20 years, 8 months

Andreas Jaeger

Hi Xemacs-Patchers, I thought the following might be of interest to you. We (glibc developers) received a bug report about emacs-20.3 with glibc 2.1.1. I can't reproduce this with XEmacs 21.0p2. Nevertheless the patch looks fine (I'm just running a mule-enabled XEmacs 21.0p2 with it) and should work with glibc 2.0 and 2.1 (I only tested with glibc 2.1.1). Andreas -- Andreas Jaeger aj(a)arthur.rhein-neckar.de jaeger(a)informatik.uni-kl.de for pgp-key finger ajaeger(a)aixd1.rhrk.uni-kl.de

1 participants
0 comments

Re: Terminology 20 years, 8 months

Didier Verna

Charles G Waldman <cgw(a)fnal.gov> writes: > How come it's M-x remove-directory to get rid of a directory, but > M-x delete-file to do the same thing to a file? Because deleTTT-DDDDirectory and remoVVV-FFFile aren't easy to pronouce :-) -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Terminology 20 years, 8 months

Charles G Waldman

How come it's M-x remove-directory to get rid of a directory, but M-x delete-file to do the same thing to a file? Just wondering...

1 participants
0 comments

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 May 1999