> > source /sw/etc/profile.d/xfontpath.csh > > if ( -x /sw/bin/xfontpath && 1 ) then > > if ( x:0.0 = x:0.0 ) then > > tcsh: if: Expression Syntax. > > > > /sw/etc/profile.d/xfontpath.csh should read > > > > if ( -x "/sw/bin/xfontpath" && $?DISPLAY ) then > > if ( "x$DISPLAY" == x:0.0 ) then > > ( "/sw/bin/xfontpath" enable & ) >& /dev/null > > endif > > endif > > > > Note the '==' instead of '='. > > The bash version works. > > > > Cc'd Aida who committed the new version yesterday. The bug is in the > > tarball.
I fixed the bug now. > What's the idea anyway of running xfontpath only if DISPLAY is set to > ":0.0"? I don't understand this at all. In my case it will not be > enabled ever, because I set DISPLAY to ":0" and not to ":0.0". Sometimes > I run on display ":1", and I want to use xfontpath, too. Sometimes I run > on display "localhost:10.0", and then I don't need xfontpath, but does > it really hurt if xfontpath is run in situations where it is not needed? The xfontpath at a wrong host breaks many things. We must be conservative to change font paths. Technically, profile.d is a wrong place to setup font paths. It should be moved into xinitrc.d. But it is too backward-incompatible decision to make by myself. In addition, I want to make another incompatible change, i.e. change xfontpath.conf format to distinguish TTCap fonts.dir's and others. Such incompatible changes should be made at once by the core team. I posted relate suggestions to fink-devel@, but no response... ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
