> I'm wondering now if it has to do with me using this line:
>        exec /usr/bin/$wm > .${wm}.errors 2>&1
> as opposed to:
>        /usr/bin/$wm > .${wm}.errors 2>&1
> I'm going to test that now.

Don't see why that would matter.

If you're tired of searching, though, and just want a solution, here's
a suggestion.  I put all of my complicated bash setup stuff into a
directory called ~/.bashscripts.  One of those scripts is called
setpaths.  Then my .bashrc, .bash_profile, or whichever can just
source ~/.bashscripts/setpaths and get a standard environment
(including LD_LIBRARY_PATH), but if I need to change it I only have to
modify one file.

The downside is that if you use this method in .bashrc and someday you
extend a path at the command line and then execute a subshell, you'll
wind up with the unextended path.
    Geoff Kuenning   geoff cs hmc edu

McDonald's, which does not wait on your table, does not cook your food
to order, and does not clear your table, came up with the slogan ``We
Do It All For You.''
	-- Dave Barry

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]