April 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Properties and readonly objects 25 years, 2 months

Jan Vroonhof

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_. Probably in this case it is interned at that time (although I do not know how). I agree the code you cited from bytecode.c looks correct. I also read through it when hunting fro this bug. > > > 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. > > However, this is incomplete. What happens if I unintern it later (as > > x-win-init-sun does)? > > If you unintern it later, it doesn't matter, because you still have a > living reference in Vpure_uninterned_symbol_table, which should keep > the GC sweeper from putting its greasy hands on the symbol. No. That reference exists only if it was uninterned before. I still think that is the best explanation for the crash, giving the symptoms. Jan

1 participants
0 comments

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

Jan Vroonhof

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. What i meant that with the above setting it should not be needed to redefine kill frame. Jan

1 participants
0 comments

Re: italic font size 25 years, 2 months

Raymond Toy

>>>>> ">" == 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? :-) Ray

1 participants
0 comments

auth 2ec98bf6 subscribe xemacs-beta Kuang Hwa Lin 25 years, 2 months

Kuang Hwa Lin

auth 2ec98bf6 subscribe xemacs-beta Kuang Hwa Lin

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: >> (defun delete-frame-or-save-buffers-kill-emacs (&optional frame) >> "If there is only one frame, `save-buffers-kill-emacs', else `delete-frame'." >> (interactive) >> (delete-frame frame t)) >> >> (global-set-key [(control x) (5) (0)] 'delete-frame-or-save-buffers-kill-emacs) > (setq allow-deletion-of-last-visible-frame t) Actually, this does not have any affect on the second argument to `delete-frame'. -- 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: >>> Anyway, you may get a better result with the following in your .emacs: >>> (setq *try-oblique-before-italic-fonts* t) > Does this still work for you in 21.0.66 and later? It stopped working > for me and I haven't had a chance to look into why. Ugh, you're right. I have my X resources set correctly, and without them, I get an italic font which is not only ugly, but a slightly different size from my regular. I think that the problem is that the italic font is built before .emacs is read. bold-italic is even worse off, since `x-make-font-bold-italic' doesn't honor *try-oblique-before-italic-fonts* (yet). > I can always use X resources for this, but I've been trying to move > away from that and setting everything in lisp. I agree. -- Colin

1 participants
0 comments

Re: italic font size 25 years, 2 months

Raymond Toy

>>>>> ">" == Colin Rafferty <craffert(a)ms.com> writes: >> Anyway, you may get a better result with the following in your .emacs: >> (setq *try-oblique-before-italic-fonts* t) Does this still work for you in 21.0.66 and later? It stopped working for me and I haven't had a chance to look into why. The splash screen shows a yucky bold italic font, which must be generated from the italic courier font instead of oblique courier font. I can always use X resources for this, but I've been trying to move away from that and setting everything in lisp. Ray

2 participants
1 comments

Re: bug report: cl-extra version 2.02, equalp 25 years, 2 months

Hrvoje Niksic

The following message is a courtesy copy of an article that has been posted to gnu.emacs.bug as well. [ For xemacs-beta folk: equalp is broken in XEmacs; (equalp '(1 2) '(1 3)) returns t ] daveg(a)synaptics.com (Dave Gillespie) writes: > No, the correct code is this: > > ((consp x) > (while (and (consp x) (consp y) (equalp (car x) (car y))) > (cl-pop x) (cl-pop y)) > (and (not (consp x)) (equalp x y))) > > BTW, I don't know what the "XEmacs change" comment refers to, > since the lines that follow it are unchanged from my original > code as far as I can tell. The comment probably refers to those lines being different to what is in FSF Emacs. I'll apply your fix to XEmacs source; thanks.

1 participants
0 comments

Re: italic font size 25 years, 2 months

Colin Rafferty

Itai Ben-Yaacov writes: > 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. I'm not sure why this is happening. Are you sure that you have italic courier fonts in 120? Anyway, you may get a better result with the following in your .emacs: (setq *try-oblique-before-italic-fonts* t) > 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... :( But that is not solving your problem really, since you are just losing the italic font altogether (by making it regular). If the previous hint doesn't work, try this, instead: Emacs.italic.attributeFont: -*-courier-medium-o-*-*-*-120-*-*-*-*-*-* Emacs.bold.attributeFont: -*-courier-bold-r-*-*-*-120-*-*-*-*-*-* Emacs.bold-italic.attributeFont: -*-courier-bold-o-*-*-*-120-*-*-*-*-*-* Of course, if you don't have these fonts, then that's what XEmacs is really having a problem with. -- Colin

1 participants
0 comments

Re: Properties and readonly objects 25 years, 2 months

Hrvoje Niksic

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > >> Another is that you can optimize GC with this kind of knowledge. > >> It seems that, since reachability is affected by mutable plists, > >> you want the plists of immutable objects to be immutable as well. > > Hrvoje> Hmm. The old "pure" stuff behaved this way for strings. It > Hrvoje> took the easy way out for symbols, simply refusing to create > Hrvoje> pure symbols. > > Can't strings also have plists? Of course. That's why I said that the old stuff behaved this way for strings; by "this way" I referred to what you stated about immutable object's plists being immutable as well.

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