On Fri, Apr 8, 2016 at 12:35 AM, Jamie Zawinski <[email protected]> wrote: > If you modify xscreensaver to not obey $PATH, you are making it do this > weird, confusing, undiscoverable thing. > > If you merely launch it with a different $PATH, then it's easy to know what's > going on. Especially since the $PATH appears in error messages about not > being able to find things.
I see the point with PATH being listed in error messages. Setting the path or not obeying the provided one seems to me pretty much the same (for locating hacks), so I am fine with that too. But let me be clear, I am only talking about the part "let's start the hack with name X". For running helpers etc it would be nice to have a reasonable PATH so xscreensaver-get-images & friends can be found without that we force full paths on them, or clumsy soft links in /usr/lib/xscreensaver - this would get messy since "friends" can involve a lot of dependencies. Is it not possible to say, when X is a name in preferences that has no path, to run /usr/lib/xscreensaver/X but with full (unmodified) PATH? > >> Is it not possible to specify the full path in the app-default file? > > You could do that, but just changing $PATH seems a lot simpler, and isn't > going to result in merge conflicts for the rest of eternity. I meant for the users if they want to add their own hack. I did not mean we should add full path to the hacks we ship in /usr/lib/xscreensaver. Definitely would like to avoid patching the app-defaults more than necessary :) Tormod
