September 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: XEmacs' desktop icon greyed out in 21.2 24 years, 7 months

ALTMARK＠de.ibm.com

I'm sitting on a 7043 Model 43P-150 with a GXT255P graphics adapter installed. As this card has 24-bit true color depth and allows to display 16.7 million colors *simultaneously*, I can't imagine this should be a problem. As a matter of fact, it doesn't make a difference if I change from "more colors for applications" (which is my default) to "more colors for desktop". What confuses me, is that the 21.2-b11 binary starts with a correctly displayed icon - with the window manager having the same settings, with the same graphics adapter and also with my X settings unchanged. Thus something must have changed since b11 ... Another confusing effect: XEmacs 21.1.7, compiled with the *same* environment on the *same* machine, works fine, i.e. has the correct colored icon. This is why is suspect 21.2 to do something wrong. To the Motif problems: I've also worked with former beta releases of 21.2, but never had any problems. Maybe I just had a lot of luck ...! ;-) Or is it because I compiled using the Motif 1.2 compatibility files as includes to the compiler (see Installation file), which was the only way it worked for me. Finally, thanks for the hint concerning X11.base.lib. Of course I have it installed (4.3.2.6) - in fact I was as happy as you when IBM finally fixed this. I can remember that several XEmacs applications (shell, compile, etc.) caused a crash before this was fixed. I was just thinking about building against stock X11, when the fix was made available. Nevertheless, thank you for mentioning it! --- Markus Alt IBM Laboratory Boeblingen, Germany Valdis.Kletnieks(a)vt.edu on 09/29/99 03:27:40 PM Please respond to Valdis.Kletnieks(a)vt.edu To: Markus Alt/Germany/IBM＠IBMDE cc: xemacs-beta(a)xemacs.org Subject: Re: XEmacs' desktop icon greyed out in 21.2 On Wed, 29 Sep 1999 10:52:46 +0200, ALTMARK(a)de.ibm.com said: > Nevertheless, finally: Since a few beta versions of 21.2, the desktop icon of > XEmacs is displayed greyed-out on my window manager (i.e. not that usual colored > red, yellow and white style). Same for dtwm and mwm window manager. I don't > remember exactly in which version this occured for the first time, but it > definetely happens when I start the latest 21.2-b19 (compiled from the tarballs) > and on the other hand everything's ok when I start that old 21.2-b11 binary I > still have (also compiled myself). As I haven't built each and every version in > between, I can't determine when I saw this first. What model RS/6000 are you on, and what graphic card is installed? This sounds suspiciously like colormap exhaustion on an 8-bit card, where it ends up trying to find the "closest" already allocated color if all 256 colormap cells are installed. Under dtwm, go into the 'preferences' panel, and look under 'colors' - does setting "more for applications" or "more for desktop" make a difference? > Surprisingly, when opening the file > <installdir>/lib/xemacs-21.2-b19/etc/xemacs-icon.xpm within XEmacs and call "M-x > xpm-mode" afterwards, the XPM image is displayed as expected at the top of the > buffer. If you're running with "more colors for applications", XEmacs may be able to get 192 or so color cells, and be able to display it "right", but with onlu 16/32 or whatever it is reserved for the window manager, it's mapping down to some other color (since icon colors count against the window manater, not against the application). > Perhaps somebody can shed a little light on this? OS is AIX 4.3.2, Installation > file attached below. (BTW, when talking about the Installation file: It always > complains that "Motif dialog boxes cause problems on AIX 4.3 and higher". I've > never seen any of them ... What problems are these?) Umm.. The usual problem is the XEmacs process bombing out with a signal 6 at startup time while trying to initialize the first frame. You'd know it if you saw it. ;) There appear to be *some* combinations of *exact* levels of XEmacs and Motif that don't bomb out, probably more due to luck than anything else. (For example, for the 21.2 betas, Motif was broken up to -b12 or so, started working till -b17, and is broken again. I can't be sure if it was -b12 through -b17, or if it was X11.libs.motif.4.3.2.foo for some values of foo, or an interaction). If it's working now, it will probably fall over the next time you apply a patch. ;) Oh, since you're on AIX 4.3.2, make sure to install X11.base.lib 4.3.2.5 or later to pick up a *very* important fix for libXt.a. It's free, and easy to do. ;) -- Valdis Kletnieks Computer Systems Senior Engineer Virginia Tech

2 participants
1 comments

Re: [Jens Elkner <elkner@ue.iff.fhg.de>] RFE: Install doc 24 years, 7 months

William M. Perry

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Jeff Miller <jmiller(a)smart.net> writes: > > > and, if you do have xemacs speak http at that point, aren't you going > > to be requiring it to have xemacs-base, and chunks of w3 installed? > > It needs to be a heavily stripped down version of w3 yes. The work > involved is the reason this isn't done yet. However I would prefer that > over EFS as nowadays _if_ you have net access your just as likely to have > http access and this can be done without the use of external programs. The only thing you would need would be the URL package, and if you want _seriously_ stripped down HTTP functionality, you don't even need that. If you remove things like authentication, cookies, and stuff like that, the CORE HTTP functionality of Emacs/W3 is less than 600 lines of code, and could be easily stripped out into an 'http-lite.el' I agree that using HTTP instead of EFS is probably a win, especially on windows w/o cygwin. -Bill P.

1 participants
0 comments

Re: [Jens Elkner <elkner@ue.iff.fhg.de>] RFE: Install doc 24 years, 7 months

Jan Vroonhof

john s jacobs anderson <jacobs(a)azstarnet.com> writes: > the message below came into webmaster(a)xemacs.org. as near as i can > tell, he is having difficulties due to not properly installing the > packages. is that a correct reading? Yep. However part of the problem is that "make install" is not creating the approriate directories as a template. In that situation the package installation utilities have horendous failure modes. If you do install the xemacs-base and efs packages by hand then first then it will work. I guess I sure wouldn't veto a patch that unpackaged a copy of EFS and/or xemacs-base at "make install" provided they can be upgraded as normal packages. (The better solution would be to have XEmacs talk http to bootstrap). > "The XEmacs Packages Quick Start Guide" - Installing by Hand is wrong: > cd $prefix/lib/xemacs/xemacs-packages or cd $prefix/lib/xemacs/mule-packages > is wrong, cd $prefix/lib/xemacs is right for both, xemacs-sumo.tar.gz > and xemacs-mule-sumo.tar.gz since the xemacs-packages and mule-packages > are already in the archive. No it is correct. The procedure for installing a sumo tarball is given just above it and does contain $prefix/lib/xemacs. However being correct doesn't help if it still confuses users :-( Jan

3 participants
2 comments

XEmacs' desktop icon greyed out in 21.2 24 years, 7 months

ALTMARK＠de.ibm.com

Maybe I should have reported this much earlier, but perhaps I got used to that odd behaviour ... Nevertheless, finally: Since a few beta versions of 21.2, the desktop icon of XEmacs is displayed greyed-out on my window manager (i.e. not that usual colored red, yellow and white style). Same for dtwm and mwm window manager. I don't remember exactly in which version this occured for the first time, but it definetely happens when I start the latest 21.2-b19 (compiled from the tarballs) and on the other hand everything's ok when I start that old 21.2-b11 binary I still have (also compiled myself). As I haven't built each and every version in between, I can't determine when I saw this first. Surprisingly, when opening the file <installdir>/lib/xemacs-21.2-b19/etc/xemacs-icon.xpm within XEmacs and call "M-x xpm-mode" afterwards, the XPM image is displayed as expected at the top of the buffer. Perhaps somebody can shed a little light on this? OS is AIX 4.3.2, Installation file attached below. (BTW, when talking about the Installation file: It always complains that "Motif dialog boxes cause problems on AIX 4.3 and higher". I've never seen any of them ... What problems are these?) TIA for your help! (See attached file: Installation) --- Markus Alt IBM Laboratory Boeblingen, Germany

2 participants
1 comments

Re: [Jens Elkner <elkner@ue.iff.fhg.de>] RFE: Install doc 24 years, 7 months

Jan Vroonhof

Jeff Miller <jmiller(a)smart.net> writes: > and, if you do have xemacs speak http at that point, aren't you going > to be requiring it to have xemacs-base, and chunks of w3 installed? It needs to be a heavily stripped down version of w3 yes. The work involved is the reason this isn't done yet. However I would prefer that over EFS as nowadays _if_ you have net access your just as likely to have http access and this can be done without the use of external programs. In the mean time a solution that sticks EFS and xemacs-base where they belong as part of "make install" would be enough. Jan

1 participants
0 comments

Re: [Jens Elkner <elkner@ue.iff.fhg.de>] RFE: Install doc 24 years, 7 months

Michael Sperber

>>>>> "Jeff" == Jeff Miller <jmiller(a)smart.net> writes: >>>>> "JV" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: JV> I guess I sure wouldn't veto a patch that unpackaged a copy of EFS JV> and/or xemacs-base at "make install" provided they can be upgraded as JV> normal packages. (The better solution would be to have XEmacs talk JV> http to bootstrap). Jeff> re: the http bootstrap, don't forget there are still some of us poor Jeff> suckers that work at places with no internet connection whatsoever. Jeff> and, if you do have xemacs speak http at that point, aren't you going Jeff> to be requiring it to have xemacs-base, and chunks of w3 installed? How about something which just recognizes (or can be told) local locations for xemacs-base and efs and auto-installs them? -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: endless loop for Chinese/Cyrillic language support in 21.1.7 24 years, 7 months

Jan Vroonhof

Andreas Jaeger <aj(a)suse.de> writes: > The problem I'm reporting might be a problem of keeping 21.2 beta and > mule-base in synch - but this way 21.1.7 doesn't work correctly with > the current mule-base files. I decided therefore to send this to > xemacs-beta in the hope to get some clarifying comments if my approach > is the right way. I think xemacs-mule would be the better place to ask, I think your fix is correct (I think this is the way it is done in the Japanese environment). The problem is that part of a newer Mule API are trickling into to the mule-base package that shouldn't (AFAIK japanese also doesn't work with 21.1.7) :-( I hope tomohiko can help you more. Jan.

1 participants
0 comments

endless loop for Chinese/Cyrillic language support in 21.1.7 24 years, 7 months

Andreas Jaeger

The problem I'm reporting might be a problem of keeping 21.2 beta and mule-base in synch - but this way 21.1.7 doesn't work correctly with the current mule-base files. I decided therefore to send this to xemacs-beta in the hope to get some clarifying comments if my approach is the right way. Ok, here's the problem: Setting language support for any Cyrillic or Chinese variant leads to the following error: Lisp nesting exceeds `max-lisp-eval-depth' The problem is an endless loop. The function set-language-environment in lisp/mule/mule-cmds.el invokes the setup-function set by set-language-info-alist. This setup function calls (for Cyrillic-ISO) setup-cyrillic-iso-environment which calls again set-language-environment: Here are the relevant calls: >From mule-base/cyril-util.el: (defun setup-cyrillic-iso-environment () "Setup multilingual environment (MULE) for Cyrillic ISO-8859-5 users." (interactive) (set-language-environment "Cyrillic-ISO")) From: lisp/mule/cyrillic.el (set-language-info-alist "Cyrillic-ISO" '((setup-function . (setup-cyrillic-iso-environment . setup-cyrillic-environment-map)) >From lisp/mule/mule-cmds.el: (defun set-language-environment (language-name) "Set up multi-lingual environment for using LANGUAGE-NAME. This sets the coding system priority and the default input method and sometimes other things." (interactive (list (read-language-name 'setup-function "Set language environment: "))) (if language-name (if (symbolp language-name) (setq language-name (symbol-name language-name))) (setq language-name "English")) (if (null (get-language-info language-name 'setup-function)) (error "Language environment not defined: %S" language-name)) (funcall (get-language-info language-name 'setup-function)) What should be done? Looking at XEmacs 21.2 beta, it seems (sorry, I don't know the code in enough details, yet) that we can remove the setup-*environment function - or replace it by an internal function. But removing the setup-function completly means that we have to change mule-cmds (?) also since otherwise the language is not displayed in the menu :-(. The appended fix gets Chinese-GB working for me - but Chinese-BIG5 does not appear anymore in the menu :-(. Could somebody with more knowledge of these functions help me to fix this? Thanks, Andreas 1999-09-29 Andreas Jaeger <aj(a)suse.de> * mule/chinese.el: Use setup-chinese-gb-environment-internal as setup function for Chinese-GB. Remove setup-chinese-big5-environment for Chinise-BIG5 since it's not needed (lead to an endless loop). --- lisp/mule/chinese.el.~1~ Wed Feb 17 14:59:31 1999 +++ lisp/mule/chinese.el Wed Sep 29 09:52:29 1999 ＠＠ -190,8 +190,7 ＠＠ nil)) (set-language-info-alist - "Chinese-GB" '((setup-function . (setup-chinese-gb-environment - . setup-chinese-environment-map)) + "Chinese-GB" '((setup-function . setup-chinese-gb-environment-internal) (charset . (chinese-gb2312 sisheng)) (coding-system . (cn-gb-2312 iso-2022-7bit hz-gb-2312)) ＠＠ -240,9 +239,7 ＠＠ (set-charset-ccl-program 'chinese-big5-2 ccl-encode-big5-font) (set-language-info-alist - "Chinese-BIG5" '((setup-function . (setup-chinese-big5-environment - . setup-chinese-environment-map)) - (charset . (chinese-big5-1 chinese-big5-2)) + "Chinese-BIG5" '((charset . (chinese-big5-1 chinese-big5-2)) (coding-system . (big5 iso-2022-7bit)) (sample-text . "Cantonese (�f�y,�s�F��) ��, �A�n") (documentation . ("Support for Chinese Big5 character set." -- Andreas Jaeger aj(a)suse.de aj(a)arthur.rhein-neckar.de for pgp-key finger ajaeger(a)aixd1.rhrk.uni-kl.de

1 participants
0 comments

Re: [Jens Elkner <elkner@ue.iff.fhg.de>] RFE: Install doc 24 years, 7 months

Michael Sperber

>>>>> "je" == Jens Elkner writes: je> To ensure, that lisp packages are ok, I tried to use the new package je> mechanism via menu as described "The XEmacs Packages Quick Start Guide". je> Unfortunately it didn't work. Thus I fiddled a little bit around, and je> found that xemacs requires packages from je> $prefix/lib/xemacs-21.1.6/ What exactly do you mean by "requires packages from"? >From a quick glance, I can see nothing in the Quick Start Guide suggesting that packages be put into $prefix/lib/xemacs-21.1.6. In fact, the very first thing it says about the location of packages is this: Local and 3rd party packages go here: $prefix/lib/xemacs/site-packages Only searched by MULE-enabled XEmacsen: $prefix/lib/xemacs/mule-packages Normal packages go here: $prefix/lib/xemacs/xemacs-packages -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

[Jens Elkner <elkner@ue.iff.fhg.de>] RFE: Install doc 24 years, 7 months

john s jacobs anderson

the message below came into webmaster(a)xemacs.org. as near as i can tell, he is having difficulties due to not properly installing the packages. is that a correct reading? ( the other suggestions [the change to gunzip.. and the link to the external libraries in the install doc] have been made. ) i'll let him know that the message was forwarded here. thanks, john. --[[message/rfc822]] From: Jens Elkner <elkner(a)ue.iff.fhg.de> Message-Id: <199909060041.CAA06928(a)monster.ue.iff.fhg.de> Subject: RFE: Install doc To: webmaster(a)xemacs.org Date: Mon, 6 Sep 1999 02:41:05 +0200 (MET DST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, I just installed from the scratch Xemacs 21.1.6 on solaris 2.7 sparc as described in your Installation doc comming with xemacs having FSF in mind. So I did: 1) utgz xemacs-21.1.6.tar.gz (utgz = gunzip -c $* | tar xvf -) 2) utgz xemacs-21.1.6-info.tar.gz 3) utgz xemacs-21.1.6-elc.tar.gz 4) cd xemacs-21.1.6 5) ./configure ... 6) make install To ensure, that lisp packages are ok, I tried to use the new package mechanism via menu as described "The XEmacs Packages Quick Start Guide". Unfortunately it didn't work. Thus I fiddled a little bit around, and found that xemacs requires packages from $prefix/lib/xemacs-21.1.6/ but looks them up in $prefix/lib/xemacs/xemacs-packages (which doesnt exist at that point) and _NOT_ in $prefix/lib/xemacs-21.1.6/. So moving $prefix/lib/xemacs-21.1.6 to $prefix/lib/xemacs/xemacs-packages gave me at least the Options/Manage Packages Filemenu. And to initiate Packages updates. Unfortunately it didn't work as well! After a little closer look I found out, that there must me something else with the xemacs-packages! Thus I downloaded xemacs-mule-sumo.tar.gz and xemacs-sumo.tar.gz, moved back the old packages ( mv $prefix/lib/xemacs/xemacs-packages $prefix/lib/xemacs-21.1.6/ ) and installed the sumos - next error: "The XEmacs Packages Quick Start Guide" - Installing by Hand is wrong: cd $prefix/lib/xemacs/xemacs-packages or cd $prefix/lib/xemacs/mule-packages is wrong, cd $prefix/lib/xemacs is right for both, xemacs-sumo.tar.gz and xemacs-mule-sumo.tar.gz since the xemacs-packages and mule-packages are already in the archive. After that everything works quite nice - even the update feature :) ---end of experience --- So I would recommend a QuickInstall.doc or an Overview section as described below at the very beginning of Installation file coming with the xemacs-X.Y.Z.tar.gz: Quick Install Overview ---------------------- 0) if you like, download and install optional libraries (see http://www.xemacs.org/Download/optLibs.html ) 1) cd $tmp 2) unpack xemacs-X.Y.Z.tar.gz 3) unpack xemacs-X.Y.Z-info.tar.gz 4) NOTE: if you want to install xemacs-*sumo.tar.gz packages, skip this step unpack xemacs-21.1.6-elc.tar.gz !!! xemacs team should be informed to fix that package, so that upgrading or installing packages works out from the scratch !!! 5) cd xemacs-X.Y.Z 6) ./configure --options (see INSTALLATION for detailed information) 7) make 8) make install 9) if you do not want to install xemacs-*sumo.tar.gz packages, you are done. 10) download xemacs-sumo.tar.gz and optional xemacs-mule-sumo.tar.gz 11) cd $prefix/lib/xemacs 12) unpack xemacs-sumo.tar.gz and optional xemacs-mule-sumo.tar.gz 13) take a breath and have a beer ;-) Please, just give a note to the xemacs team, if one chooses not to install+ the sumo packages, xemacs doesnt work as expected. So they should copy the initial lisp packages to $prefix/lib/xemacs/xemacs-packages or they should change the default behavior, so that xemacs also looks up the $prefix/lib/xemacs-X.Y.Z path as well (maybe its only a bug in the current version). That's it. Have fun, Jens. BTW: Thanx for xemacs - I like programming, news reading and debugging in conjuction with Sun C++ Workshop >= 4.x very very much :) -- +---[ Jens Elkner ]------------------------------[ USG IFF FhG Magdeburg ] | Certified Master Unix Systems Administrator elkner(a)usg.iff.fhg.de | | Sandtorstr. 22 http://www.ue.iff.fhg.de | | 39106 Magdeburg GERMANY http://www.ims-gmbh.server.de | +------------------------------------------------------------------------+ -- ------------------------------------------------------------------------ John S Jacobs Anderson Apprentice Geek jacobs(a)azstarnet.com Journeyman Molecular Biologist <URL:http://www.azstarnet.com/~jacobs/> <- GeneHack:bioinfo*linux*opinion

2 participants
1 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 September 1999