April 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Raymond Toy

>>>>> ">" == Colin Rafferty <craffert(a)ms.com> writes: >> Raymond Toy writes: >>>>>>> ">" == Colin Rafferty <craffert(a)ms.com> writes: >>>> bold-italic is even worse off, since `x-make-font-bold-italic' doesn't >>>> honor *try-oblique-before-italic-fonts* (yet). >> Especially noticeable in the splash screen! :-) Do this mean you'll >> have a patch for this? :-) >> Uh, no. >> I have a patch for `x-make-font-bold-italic' to work properly, but I >> don't see how to get the italic/bold/bold-italic fonts set after >> .emacs. Yeah, I did the obvious change to x-make-font-bold-italic. It obviously gets run too late for *try-oblique-before-italic-fonts* to have any effect on the splash screen. >> I'm not sure that it's possible, since you may want to change your >> fonts in .emacs, and we don't want them to then be overridden by >> make-font-italic and friends. But it *was* possible because it worked in b65 and earlier. If the font already exists we shouldn't touch it.[1] Would it be possible to defer all settings of fonts and to defer the splash screen until *after* .emacs is run? I guess I should look up what changed between b65 and b66 that could cause the effect we're seeing. (I need more hours in a day!) Ray Footnotes: [1] Spoken by a person who has no idea how and when fonts are set up. :-)

1 participants
0 comments

Missed patch to etags.el 25 years, 2 months

Malcolm Box

The following patch : http://www.xemacs.org/list-archives/xemacs-patches/9810/msg00057.html appears to have missed being applied. I believe it has been reviewed and approved. Cheers, Malcolm -- Malcolm Box malcolm(a)brownale.demon.co.uk

1 participants
0 comments

Re: Crash in XEmacs 21.0 "20 minutes to Nikko" with gnuserv/gnuclient 25 years, 2 months

Colin Rafferty

Jan Vroonhof writes: > Colin Rafferty <craffert(a)ms.com> writes: >> > (setq allow-deletion-of-last-visible-frame t) >> >> Actually, this does not have any affect on the second argument to >> `delete-frame'. > Apart from rendering it useless. Not at all. Check out the code from delete_frame_internal() in frame.c: if (!force && !allow_deletion_of_last_visible_frame && !other_visible_frames_internal (f, called_from_delete_device)) error ("Attempt to delete the sole visible or iconified frame"); If `force' (the second argument to the function) is t, then we will never get the error, and will call `save-buffers-kill-emacs. -- Colin

1 participants
0 comments

Re: italic font size 25 years, 2 months

Colin Rafferty

Raymond Toy writes: >>>>>> ">" == Colin Rafferty <craffert(a)ms.com> writes: >>> bold-italic is even worse off, since `x-make-font-bold-italic' doesn't >>> honor *try-oblique-before-italic-fonts* (yet). > Especially noticeable in the splash screen! :-) Do this mean you'll > have a patch for this? :-) Uh, no. I have a patch for `x-make-font-bold-italic' to work properly, but I don't see how to get the italic/bold/bold-italic fonts set after .emacs. I'm not sure that it's possible, since you may want to change your fonts in .emacs, and we don't want them to then be overridden by make-font-italic and friends. -- Colin

1 participants
0 comments

21.2.13 make fails on sun 25 years, 2 months

Itai Ben-Yaacov

i tried to compile 21.2.13 on a sun. after the first problem, of the -Bexport which i removed, it failed like this: . . . Loading site-load... (296) Finding pointers to doc strings... Finding pointers to doc strings...done Dumping under the name xemacs Purespace usage: 789704 of 789704 (100%). Testing for Lisp shadows ... make[2]: Leaving directory `/users/98/maths/pezz/private/build/xemacs-21.2.13/src' make[1]: Leaving directory `/users/98/maths/pezz/private/build/xemacs-21.2.13/src' Building finder database ... xemacs exiting.Opening input file: No such file or directory, /users/98/maths/pezz/private/build/xemacs-21.2.13/lisp/.#finder-inf.el make: *** [lisp/finder-inf.el] Error 255 yuck. why? btw, what is the difference between the 21.0 and the 21.2 series? for those who are interested, i ran: ./configure \ --gung-ho \ --prefix=$HOME/local \ --debug=no \ --error-checking=none \ --memory-usage-stats=no \ --dynamic=yes \ --with-clash-detection and got in return: XEmacs 21.2-b13 "Demeter" configured for `sparc-sun-solaris2.6'. Where should the build process find the source code? /users/98/maths/pezz/p rivate/build/xemacs-21.2.13 What installation prefix should install use? /users/98/maths/pezz/l ocal What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno- switch 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? /usr/dt/include /usr/X 11R6/include Where do we find X Windows libraries? /usr/dt/lib /usr/X11R6 /lib Runtime library search path: /usr/dt/lib:/usr/X11R6 /lib:/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 native sound support. Compiling in support for GNU DBM. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in EXPERIMENTAL support for Drag'n'Drop ( CDE ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. Clash detection will use "${statedir}/${PROGNAME}/lock" for locking files. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. thanks in advance (as always) itay -- Itaï Ben-Yaacov Ecole Normale Superieure 45, Rue d'Ulm Paris 75005 Tel.: +33-(0)155421487 Email: pezz(a)ens.fr

1 participants
0 comments

italic font size 25 years, 2 months

Itai Ben-Yaacov

Hi I have encountererd something quite bizzare: italic fonts tend to be larger than the normal ones: if i set: Emacs.default.attributeFont: -*-courier-medium-r-*-*-*-120-*-*-*-*-*-* italics are larger than 160. if i set it to 100, italics are still larger even then 120. If i set: Emacs.default.attributeFont: -*-courier-medium-r-*-*-*-120-*-*-*-*-*-* Emacs.italic.attributeFont: -*-courier-medium-r-*-*-*-120-*-*-*-*-*-* all goes fine, till i use info: the info node face, whice is bold italic, goes again larger than should be... :( anyone see something like that? my "installation": uname -a: SunOS corvette 5.5 Generic_103093-14 sun4m sparc SUNW,SPARCstation-5 ./configure '--gung-ho' '--prefix=/users/98/maths/pezz/local' '--debug=no' '--error-checking=none' '--memory-usage-stats=no' '--dynamic=yes' '--with-clash-detection' XEmacs 21.0-b67 "20 minutes to Nikko" configured for `sparc-sun-solaris2.5'. Where should the build process find the source code? /users/98/maths/pezz/private/build/xemacs-21.0.67 What installation prefix should install use? /users/98/maths/pezz/local What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch 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? /usr/dt/include /usr/X11R6/include Where do we find X Windows libraries? /usr/dt/lib /usr/X11R6/lib Runtime library search path: /usr/dt/lib:/usr/X11R6/lib:/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 native sound support. Compiling in support for GNU DBM. Compiling in support for ToolTalk. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. Clash detection will use "${statedir}/${PROGNAME}/lock" for locking files. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. thanks, -- Itaï Ben-Yaacov Ecole Normale Superieure 45, Rue d'Ulm Paris 75005 Tel.: +33-(0)155421487 Email: pezz(a)ens.fr

2 participants
1 comments

Re: Properties and readonly objects 25 years, 2 months

Hrvoje Niksic

Olivier Galibert <galibert(a)pobox.com> writes: > On Tue, Apr 13, 1999 at 11:05:16AM +0200, Hrvoje Niksic wrote: > > BTW, why do we want Lisp-level readonly objects in the first place? > > Ben wanted them to be able to give out complex structures without > having to copy them. Oh, I see. Yes, read-only strings would be very useful, for one. For example, symbol name strings could be immutable. I guess we'd need it in Lisp to be able to move some C code to Lisp. That's the only reason that would make sense.

1 participants
0 comments

Re: Properties and readonly objects 25 years, 2 months

Hrvoje Niksic

Olivier Galibert <galibert(a)pobox.com> writes: > Should put and remprop be accepted on lisp-level readonly objects? I don't know. It might make sense both ways. BTW, why do we want Lisp-level readonly objects in the first place? Do other Lisp flavors (such as CL) have them?

2 participants
1 comments

Re: Properties and readonly objects 25 years, 2 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Hrvoje Niksic <hniksic(a)srce.hr> writes: > > > If the vector is in pure space, then all its symbol contents > > should be interned in Vpure_uninterned_symbol_table until the end > > of time, and GCPRO'ed through that. If that doesn't happen, it's > > a bug in the whatever code produces the pure compiled function. > > No. In the code you quoted from Fpurecopy symbol is only put in > Vpure_uninterned_symbol_table when it is uninterned _at the time of > the purecopy_. You are right. Maybe the solution is simply to always store the symbol referenced by a pure structure to Vpure_uninterned_symbol_table. Does uncommenting the "if (!NILP (XSYMBOL (obj)->obarray)) return obj;" part fix your crash? If yes, we should investigate how large the Vpure_uninterned_symbol_table ends up. If not very large, then that's probably a good fix. The "pure space" thing will not exist in 21.2 anyway. > > > I am not sure this what Martin actually fixed. > > > > You mean Kyle? > > I was replying to a message from Gunnar in the bug tracking archive > where he asks the bug reporter to try it with 21.2 because Martin > had touched the relevant code. The Vpure_uninterned_symbol_table stuff was introduced by Kyle. I thought you referred to that.

1 participants
0 comments

Re: italic font size 25 years, 2 months

Raymond Toy

>>>>> "Itai" == Itai Ben-Yaacov <pezz(a)clipper.ens.fr> writes: Itai> well, it DOESNT work for me. and it seems that this IS the problem: on my Itai> system the italic font are in weird sizes, the oblique are right. Itai> just a layman's question, though a bit off the subject: what's the Itai> difference between oblique and italic? and why the wrong sizes in italics? This is based on my very limited understanding of X11 and fonts, and may be specific to my machine/setup on Solaris. The standard bitmapped X11 font for adobe-courier calls its italic font "oblique" instead of "italic". From a non-typography view, I think they're just different names for the same thing, but I may be wrong. However, if you have Type1 scalable fonts available (as I do), I think when xemacs requests an italic version of adobe-courier, the X11 server sees that there is an adobe-courier Type1 font and tries to render an italic version. This is the ugly. Itai> and why doesnt *try-oblique-before-italic-fonts* do its job? That was what it was for and obviously something changed between b65 and b66 so that it doesn't. Ray

3 participants
2 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 April 1999