Re: Fvwm Themes problem with PATH

[Dan E. <da...@mk...>]

Mikhael Goikhman <mi...@ho...> writes:
> On 08 Mar 2001 17:51:27 -0500, Dan Espen wrote:
> > 
> > Last time I ran fvwm themes I had some problems because I don't have
> > fvwm2 in my path.  What I do have in my path is a shell that starts fvwm2.
> > 
> > I don't know if you were trying to fix that with the logic I see
> > in fvwm-themes-start that tries to change the path, but it didn't
> > work.  Basically, the logic doesn't update my path since there is an
> > fvwm2 shell in my path.  Unfortunately, I tried to use this same shell
> > to start fvwm-themes which got me nowhere.  If I ever start using fvwm
> > themes, I would still like to use the fvwm2 shell to start it.
> 
> Yes, I tried to fix a case when there is a wrong/old fvwm2 in the path.
> Ok, I think I have fixed several Solaris problems in cvs.
> 
> Why exactly your fvwm2 script can't run "fvwm2 -f themes-rc"? :-)
> Does it preserve arguments in "$@"?

No, $*.

It seemed to eat up arguments until it wouldn't execute.

> > Anyway, my suggestion is when you try to exec fvwm2 near the
> > end of the shell, why don't you use the full path to start it?
> 
> There are pros and cons. I may rething this later.
> The script gets --fvwm option to change the executable (default: fvwm2).
> You may use it to force your script instead of the true fvwm2.

I'm still not sure what would be good regarding the path
but you could do:

case `which fvwm2` in
  BUILTINPATH/fvwm2) UPDATE PATH;;
esac
case `which fvwm-themes-config` in
  BUILTINPATH/fvwm-themes-config) UPDATE PATH;;
esac

> > I don't know if thats a good idea or not, but thats what I had to do
> > to get this started.
> > 
> > I have display problems now, large parts of my screen appear
> > transparent or are not updating when exposed.  I guess thats an fvwm2
> > problem.  I'm running on Solaris, displaying with Exceed.
> 
> We may do a work around in fvwm-themes if we know what happens.

I think just about anything you do in fvwm themes should not cause
windows to display incorrectly.

> You asked whether $prefix (/usr/local) is used. The answer: depends on the
> instalation, by default - no, the original directories of fvwm are used.
> Only when someone specifies --prefix, it is used (documented in INSTALL).

Ok, it just looks strange in the shell when it doesn't even exist.

--
Dan Espen
444 Hoes Lane  Room RRC 1C-214           E-mail: da...@mk...
Piscataway, NJ 08854                     Phone: (732) 699-5570