On Tue, Aug 5, 2014 at 3:06 AM, Kempf, Stephen wrote:
> I’ve run into a case, which I believe is a bug, in which a user’s .rc file
> (for whichever shell is in the SHELL env var) interferes with the commands
> run by parallel. For example:
In the next release $SHELL is ignored if GNU Parallel c
Ole Tange writes:
> In the next release $SHELL is ignored if GNU Parallel can figure out
> which shell it is started from, so if started from tcsh, 'tcsh -c'
> will be used to start new commands.
I humbly suggest you don't do that or at least make it optional. It
would make using a fancy interact
Thanks for your reply. You're absolutely right about aliases and functions -
in fact, lack of that behavior is a pet peeve of mine regarding xargs and find
-exec. I habitually forget that unlike environment settings, alias and
function definitions are not inherited by subprocesses.
For the pu
On Tue, Aug 5, 2014 at 6:49 PM, Achim Gratz wrote:
> Ole Tange writes:
>
>> In the next release $SHELL is ignored if GNU Parallel can figure out
>> which shell it is started from, so if started from tcsh, 'tcsh -c'
>> will be used to start new commands.
>
> I humbly suggest you don't do that or at
