June 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: 'italic 'bold etc faces not inheriting from default? 27 years

Hrvoje Niksic

Didier Verna <verna(a)inf.enst.fr> writes: > What about maintaining a global TODO list somewhere ? It should be > readable by everyone (on the web site of something), and we could > add stuff when ideas come (and hopefully remove stuff when it's done > ;-)) Actually, this has been proposed by Ben in a phone conversation. think it is an excellent idea. The TODO list should be somewhat like the `Futures' page, but consisting of less pie-in-the-sky stuff and more of the stuff we actually intend to work on. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- * Q: What is an experienced Emacs user? * A: A person who wishes that the terminal had pedals.

1 participants
0 comments

Re: XEmacs 21.0 and the options menu 27 years

Didier Verna

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Didier Verna <verna(a)inf.enst.fr> writes: > > > The options menu is ported to Custom, but we have no upgrade function > > from the old format to the new one. For most people, the options file is > > loaded *after* .emacs, but XEmacs 21.0 will save custom stuff in > .emacs. This > will lead to problems when people will use again the options > menu: their new > settings will be saved in .emacs, but won't have any > effect for the next > sessions since they will be overriden by the options > file. > > Not true. At least not if you do not mix versions. Note that the options > loading code generated by 20.4 does check that the version is = 20 and > therefore the options file never gets loaded under 21.x Yup. So people upgrading will believe they lost their options setting. Not much better :-( If we don't find a better solution, this should at least be documented in the NEWS file. > Even if this was not the case or if you want to support mixing version > you can get away by redefining load-options-file. The problem is more about options saving than options loading. > I thought about writing a migrate.el to convert the old options to > custom but it seems to me it is not worth it. Most of the options can > simply be copied by loading the old options file by hand once and then > doing a save-options. Wrong. The options menu saving button calls customize-save-customized. If you load the options from the old file, the options will actually be changed outside Custom, and thus the save button will not save them. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Re: 'italic 'bold etc faces not inheriting from default? 27 years

SL Baur

William M Perry <wmperry(a)aventail.com> writes: > "Kirill M. Katsnelson" <kkm(a)kis.ru> writes: >> Yes I can. This is because XEmacs font model is rotten and needs to >> be redone at all. > So lets do it for 21.1... who's with me!?!?!?!?! :) I am.

2 participants
1 comments

Re: XEmacs 21.0 and the options menu 27 years

Jan Vroonhof

Didier Verna <verna(a)inf.enst.fr> writes: > The options menu is ported to Custom, but we have no upgrade function > from the old format to the new one. For most people, the options file is > loaded *after* .emacs, but XEmacs 21.0 will save custom stuff in .emacs. This > will lead to problems when people will use again the options menu: their new > settings will be saved in .emacs, but won't have any effect for the next > sessions since they will be overriden by the options file. Not true. At least not if you do not mix versions. Note that the options loading code generated by 20.4 does check that the version is = 20 and therefore the options file never gets loaded under 21.x Even if this was not the case or if you want to support mixing version you can get away by redefining load-options-file. I thought about writing a migrate.el to convert the old options to custom but it seems to me it is not worth it. Most of the options can simply be copied by loading the old options file by hand once and then doing a save-options. That leaves the hooks stuff and the fonts. The latter is probably too difficult to do automatically and the for just the former it is too much work for too little gain IMHO. Jan

1 participants
0 comments

Re: Lisp code contributions to XEmacs? 27 years

Jari Aalto

| 98-06-11 Hrvoje Niksic <hniksic(a)srce.hr> list.xe | | I believe there will be no problems in accepting your code. XEmacs 21 | will be distributed in the forms of "packages," so all you will need | to do is create a p4 package Where should one look for the instruction how to modify .el files to support XEmacs packaging format? jari

1 participants
0 comments

RE: Beta test XEmacs/Alpha anyone? 27 years

Kirill M. Katsnelson

[CC'ed to xemacs-beta list, for someone might have laready had that problem. Paul makes the first in history attempt to natively build xemacs on NT/Alpha. Paul is not a list member, so please do not forget a carbon copy] Some time ago, Paul Bunn wrote... |+ | I'm getting an error during the build process about not being able to | create directory "\\\\.autosave". Wow, a big progress! This means that temacs already runs... Do not you get a lisp backtrace? Could you please send me all output from make (no need to rebuild all, just the last failed step is enough). Backtrace is generated by XEmacs lisp engine, in its "top level" exception handler when an exception ("lisp" exception) is not catched elsewhere upper at the stack (SEH?). It looks like Signaling: ("Cannot create directory" "\\\\.autosave") ### ... called from form... ### etc Kirill | Regards, | | Paul Bunn, BEI, 425-644-6000 | Microsoft MVP - WindowsNT | http://www.ultrabac.com |-

1 participants
0 comments

Re: Bug when selecting TTY frames 27 years

Hrvoje Niksic

greg(a)alphatech.com (Greg Klanderman) writes: > >>>>> "Kyle" == Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Kyle> > Kyle> (select-frame (next-frame)) is working as (I) intended. > > even with focus-follows-mouse set true? > > Despite the `mouse' in the name, the docs say when "set to t, then > XEmacs will not gratuitously change the keyboard focus." I would > argue this should work under tty too. Maybe. You are the Mr. focus-follows-mouse, so I'll certainly respect your judgement. However, in that case (and even without it), I would like focus-follows-mouse to be renamed to something more sensible. I've always found the name of that variable to be incredibly misleading and obfuscated. When I first saw it, I actually thought it was a minor mode to implement the focus-follows-mouse behaviour for Emacs windows! -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Jone's law: The man who smiles when things go wrong has thought of someone to blame it on.

2 participants
1 comments

Re: 'italic 'bold etc faces not inheriting from default? 27 years

William M. Perry

"Kirill M. Katsnelson" <kkm(a)kis.ru> writes: > Some time ago, Andy Piper wrote... > |+ > | Which appear to be hard-wired to Courier. Can anyone tell me why this is? > |- > > Yes I can. This is because XEmacs font model is rotten and needs to > be redone at all. So lets do it for 21.1... who's with me!?!?!?!?! :) I've got lots of it done in lisp, just need to move it to C and do all the fun merging of properties at the extent level like we do for colors, etc. -Bill P.

2 participants
1 comments

Did someone here get news ... 27 years

Didier Verna

... from the guy that contacted us once, with the plan of writing a book on XEmacs ? (I don't know why this suddenly came to my mind again). --Didier

1 participants
0 comments

Re: 'italic 'bold etc faces not inheriting from default? 27 years

Didier Verna

SL Baur <steve(a)vmailer.xemacs.org> writes: > William M Perry <wmperry(a)aventail.com> writes: > > > "Kirill M. Katsnelson" <kkm(a)kis.ru> writes: > >> Yes I can. This is because XEmacs font model is rotten and needs to > >> be redone at all. > > > So lets do it for 21.1... who's with me!?!?!?!?! :) > > I am. What about maintaining a global TODO list somewhere ? It should be readable by everyone (on the web site of something), and we could add stuff when ideas come (and hopefully remove stuff when it's done ;-)) --Didier

1 participants
0 comments

2025

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 June 1998