August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [Success] XEmacs 21.1.4 "Arches", i386-pc-win32 24 years, 9 months

Jan Vroonhof

Vin Shelton <acs(a)xemacs.org> writes: > Adrian and Jan, > Just to be clear: are you recommending that I apply this patch > Message-ID: <byaexc6i8w.fsf_-_(a)bolzano.math.ethz.ch> > to 21.1? What patch is that. Is their an easy way to lookup patches in the archive by message ID? If it is what I think it (the frob-face-property patch) then at the very least it must be combined with the fix for it that I just applied for cvs. In itself it would be no problem to upgrade frob-face-property to its 21.2.x version because it supposed to be compatible a better version. Adrian: 1. Were you implying that with the new frob-face-property 21.1.x works better. If so 2. Does the NT version of the -vanilla default face contain specifier specs that are device specific and/or have tags? In 21.1.x the default face is only face that could have something to "frob" so it is not surprising that if there are any problems, it is there. If Adrian says it works for him, upgrade to the 21.2 version. The complete one of course. Jan P.S. In the long run the whole tags based custom interface should be back-ported but it is not complete yet.

1 participants
0 comments

Re: Package-Directory silently changed (or loudly but I missed it?) 24 years, 9 months

Jan Vroonhof

Holger Schauer <Holger.Schauer(a)gmx.de> writes: > It seems that the place where packages are installed has changed - > i.e., I used to think (and this is also what the docu sayz) that newly > installed packages go to xemacs/lib/packages/<spec>-packages, with > <spec> ::= mule | xemacs | ... Yes that is where they should go. In practice however this is what pacakge-get.el uses If it was installed before --> put it in the same location, otherwise If mule package --> put it where mule-base is. Other wise --> put it where xemacs-base is. If xemacs-base is not found --> put it in (last late-packages). If you have a normal package tree (last late-packages) is "xemacs-packages". > So, when I recently did a completly new install of 21.1.4 (on a > Solaris box), I installed xemacs-base and efs right in > xemacs/lib/packages/xemacs-packages. This worked out okay. Did you restart XEmacs so it found xemacs-base? What does (package-admin-get-install-dir 'unkown) say. Jan P.S. It maybe a problem that the directory is named "packages" (as that is an old name for the package tree and 21.1.x still picks that up).

1 participants
0 comments

Re: Package-Directory silently changed (or loudly but I missed it?) 24 years, 9 months

Michael Sperber

>>>>> "Holger" == Holger Schauer <Holger.Schauer(a)gmx.de> writes: Holger> [1 <text/plain; US-ASCII (7bit)>] Holger> Hi folks ! Holger> It seems that the place where packages are installed has changed - Holger> i.e., I used to think (and this is also what the docu sayz) that newly Holger> installed packages go to xemacs/lib/packages/<spec>-packages, with Holger> <spec> ::= mule | xemacs | ... This is correct. Holger> So, when I recently did a completly new install of 21.1.4 (on a Holger> Solaris box), I installed xemacs-base and efs right in Holger> xemacs/lib/packages/xemacs-packages. This worked out okay. However, Holger> after that packages pulled in via pui installed directly in the Holger> packages dir, i.e. in xemacs/lib/packages (the packages installed were Holger> all non-mule packages). I've also seen this before with an 21.1.3 Holger> install on my linux-box. Pui, however, felt fine with the situation, Holger> i.e. it detected both efs/xemacs-base in xemacs-packages as well as Holger> all other packages in packages. I haven't looked into it more deeply Holger> since then (i.e. whether autoloads work). Hrx. It actually changed the other way. Just plain "packages" was the name of the directory in 20.4, and we changed it to be xxx-package for 21.1. However, 21.1 still accepts "packages" for compatibility reasons. 21.2 won't anymore. Someone from the pui folks may need to look into this. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Package-Directory silently changed (or loudly but I missed it?) 24 years, 9 months

Holger Schauer

Hi folks ! It seems that the place where packages are installed has changed - i.e., I used to think (and this is also what the docu sayz) that newly installed packages go to xemacs/lib/packages/<spec>-packages, with <spec> ::= mule | xemacs | ... So, when I recently did a completly new install of 21.1.4 (on a Solaris box), I installed xemacs-base and efs right in xemacs/lib/packages/xemacs-packages. This worked out okay. However, after that packages pulled in via pui installed directly in the packages dir, i.e. in xemacs/lib/packages (the packages installed were all non-mule packages). I've also seen this before with an 21.1.3 install on my linux-box. Pui, however, felt fine with the situation, i.e. it detected both efs/xemacs-base in xemacs-packages as well as all other packages in packages. I haven't looked into it more deeply since then (i.e. whether autoloads work). Holger -- --- http://www.coling.uni-freiburg.de/~schauer/ --- "Perl was the first language to integrate the Unix environment into itself." -- Per Abrahamsen in comp.emacs.xemacs

1 participants
0 comments

Re: some comments on the gutter 24 years, 9 months

Didier Verna

Andy Piper <andy(a)xemacs.org> wrote: > You can put *anything* in the gutter area. It would be nice for people to > come up with a few ideas of what would be useful. Maybe I'll make people scream but anyway: I'd like to have the echo area in the gutter. At least, I'd like to have separate places for the echo area and the minibuffer. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

1 participants
0 comments

Re: built with XEmacs icon? 24 years, 9 months

SL Baur

john s jacobs anderson <jacobs(a)azstarnet.com> writes in xemacs-beta(a)xemacs.org: > Is there a 'Built with XEmacs' icon available for use on webpages? Check out the images distributed with XEmacs in etc/. cbx.png is one such.

1 participants
0 comments

built with XEmacs icon? 24 years, 9 months

john s jacobs anderson

Is there a 'Built with XEmacs' icon available for use on webpages? I've looked on <URL:http://www.xemacs.org> to no avail, and haven't seen one anywhere else either. I feel a bit guilty, as I've got a 'Vim powered' icon and I only use that maybe 2% of the time... john, seeking truth in advertising... -- ---------------------------------------------------------------- John S Jacobs Anderson jacobs(a)azstarnet.com www.treefort.org/~jacobs/ <-- GeneHack (bioinfo*linux*opinion)

2 participants
1 comments

Re: [Success] XEmacs 21.1.4 "Arches", i386-pc-win32 24 years, 9 months

Vin Shelton

Adrian and Jan, Just to be clear: are you recommending that I apply this patch Message-ID: <byaexc6i8w.fsf_-_(a)bolzano.math.ethz.ch> to 21.1? Thanks, vin >>>>> On 09 Jul 1999, Adrian Aichner <aichner(a)ecf.teradyne.com> said: >>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> Adrian Aichner <aichner(a)ecf.teradyne.com> writes: >>> (custom-set-faces >>> - '(default ((t (:family "Courier New" :bold nil :italic nil))) t) >>> + '(default ((t (:background "white" :bold nil :italic nil))) t) >>> '(gui-button-face ((t (:foreground "black" :background "white"))) t) >>> >>> This works fine with 21.2-b17+ with your frob-face-property patch applied. >>> >>> However, the new setting for face 'default does not work for >>> 21.1-b2 >>> 21.1.3 >>> 21.1.4 Jan> Please define 'does not work' more exactly. Note that the new Adrian> Please see: Adrian> When the problem Adrian> (http://www.xemacs.org/list-archives/xemacs-beta/9906/msg00235.html) Adrian> first occured in 21.2-b16 I modified my .emacs like this: Jan> customize specifier stuff is written to fix real problems Jan> that occur when mixing old and new ways of setting the Jan> fonts. So it is not in itself surprising that there are Jan> problems with the old method. However we need to check we Jan> didn't introduce any new ones by accident in the 21.1.x Jan> series. Adrian> This is why I spent 1/4 of a night building 21.2-b2, 21.1.3, 21.1.4 Adrian> again to track down the problem. Adrian> The result is that Adrian> '(default ((t (:background "white" :bold nil :italic nil))) t) Adrian> exposes the same problem under 21.1.[2-4] Adrian> as Adrian> '(default ((t (:family "Courier New" :bold nil :italic nil))) t) Adrian> did under 21.2-b1[67] until your frob-face-property patch came along.

1 participants
0 comments

Re: Usability issues (was: horribly long Subject ;D) 24 years, 9 months

SL Baur

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: > One Major step would be "Get Red Hat to finally ship the d*mn thing!" Shipping it unbroken would be nice too. Every RedHat installation I've seen in Japan that had XEmacs on it, had a broken XEmacs. :-(

1 participants
0 comments

Possibly fix for the scan_words in minibuffer crash 24 years, 9 months

Jan Vroonhof

I think it was an off by 1 error. scan_words would do when from > limit from-- peek at from-1 Thus it could look at limit-1 (boom!) I rewrote it to use less #ifdef MULE's in the middle of the logic. It is always nice to have more "-"'s than "+"'s in a patch. 1999-08-11 Jan Vroonhof <vroonhof(a)math.ethz.ch> * syntax.c (scan_words): Unified Mule and Non-mule scanning. Word boundary search looks back instead of forward so that it doesn't peek over the limit. --- src/syntax.c~ Sat Jun 26 14:57:58 1999 +++ src/syntax.c Wed Aug 11 22:58:04 1999 ＠＠ -327,6 +327,7 ＠＠ } + #ifdef MULE /* Return 1 if there is a word boundary between two word-constituent characters C1 and C2 if they appear in this order, else return 0. ＠＠ -337,16 +338,6 ＠＠ && word_boundary_p (c1, c2)) extern int word_boundary_p (Emchar c1, Emchar c2); -#else -static int -word_constituent_p (struct buffer *buf, Bufpos pos, - struct Lisp_Char_Table *tab) -{ - enum syntaxcode code = SYNTAX_UNSAFE (tab, BUF_FETCH_CHAR (buf, pos)); - return ((words_include_escapes && - (code == Sescape || code == Scharquote)) - || (code == Sword)); -} #endif /* Return the position across COUNT words from FROM. ＠＠ -358,11 +349,10 ＠＠ { Bufpos limit = count > 0 ? BUF_ZV (buf) : BUF_BEGV (buf); struct Lisp_Char_Table *mirrortab = XCHAR_TABLE (buf->mirror_syntax_table); -#ifdef MULE Emchar ch0, ch1; enum syntaxcode code; -#endif + /* #### is it really worth it to hand expand both cases? JV */ while (count > 0) { QUIT; ＠＠ -371,40 +361,36 ＠＠ { if (from == limit) return 0; -#ifdef MULE + ch0 = BUF_FETCH_CHAR (buf, from); code = SYNTAX_UNSAFE (mirrortab, ch0); -#else - if (word_constituent_p (buf, from, mirrortab)) - break; -#endif - from++; -#ifdef MULE + if (words_include_escapes && (code == Sescape || code == Scharquote)) break; if (code == Sword) break; -#endif + + from++; } QUIT; - while ((from != limit) -#ifndef MULE - && word_constituent_p (buf, from, mirrortab) -#endif - ) + while (from != limit) { -#ifdef MULE ch1 = BUF_FETCH_CHAR (buf, from); code = SYNTAX_UNSAFE (mirrortab, ch1); if (!(words_include_escapes && (code == Sescape || code == Scharquote))) - if (code != Sword || WORD_BOUNDARY_P (ch0, ch1)) + if (code != Sword +#ifdef MULE + || WORD_BOUNDARY_P (ch0, ch1) +#endif + ) break; +#ifdef MULE ch0 = ch1; -#endif +#endif from++; } count--; ＠＠ -418,12 +404,7 ＠＠ { if (from == limit) return 0; -#ifndef MULE - if (word_constituent_p (buf, from - 1, mirrortab)) - break; -#endif - from--; -#ifdef MULE + ch1 = BUF_FETCH_CHAR (buf, from - 1); code = SYNTAX_UNSAFE (mirrortab, ch1); if (words_include_escapes ＠＠ -431,24 +412,25 ＠＠ break; if (code == Sword) break; -#endif + + from--; } QUIT; - while ((from != limit) -#ifndef MULE - && word_constituent_p (buf, from - 1, mirrortab) -#endif - ) + while (from != limit) { -#ifdef MULE ch0 = BUF_FETCH_CHAR (buf, from - 1); code = SYNTAX_UNSAFE (mirrortab, ch0); if (!(words_include_escapes && (code == Sescape || code == Scharquote))) - if (code != Sword || WORD_BOUNDARY_P (ch0, ch1)) + if (code != Sword || +#ifdef MULE + WORD_BOUNDARY_P (ch0, ch1) +#endif + ) break; +#ifdef MULE ch1 = ch0; #endif from--;

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