On Wed, 30 May 2001, Jeff Raven wrote:
> A) None. Just encourage people to use exec or & in their
> menu items. (Or force everyone to use bash :)
No. Using "exec" or "&" still starts the initial /bin/sh. Even though it
eventually closes this is a waste.
> D) Provide two menu items, say [exec] and [cexec]; the first
> would just use "sh", the second "sh -c". rootCommand would
> still use "sh -c". For the most part this would make things
> work like they used to before the exec code was changed.
> E) Provide two menu items, say [exec] and [sexec]; the first
> using "sh -c" and the second using "sh". rootCommand would
> still use "sh -c".
But what about not using any /bin/sh?
I prefer F)
F) Provide two menu items, say [shexec] and [exec]; the first
using "sh -c" and the second not using any "sh". rootCommand
would still use "sh -c". (If users want old behaviour, they would need
to change their [exec] menu entries to [shexec].)
(I am sure you saw it, but I did provide a patch that works for me the
past week.)
Jeremy C. Reed
....................................................
BSD software, documentation, resources, news...
http://bsd.reedmedia.net/
