"ifthen" for more "dynamic" argv manipulation

2016-05-24 Thread Max Ivanov
Hi, I'd like to discuss an idea of more dynamic argv manipulation. Since execline heavily relies on chain loading it becomes very important whether block is executed directly or via fork; add to that extreme importance of ENV vars as a way to carry state through chain loading and it becomes

Re: "ifthen" for more "dynamic" argv manipulation

2016-05-24 Thread Max Ivanov
Thanks for crystal clear response and for keeping design clean, while not forgetting about practical aspects of real-life use-cases. `-s` switch is what I wanted indeed. Strangely, despite writing in execline more or less for a week, concept that "nothing leaks from a block" never crossed my

Re: Documentation feedback: surprising behavior of null substitutes

2016-05-20 Thread Max Ivanov
ercot <ska-skaw...@skarnet.org> wrote: > On 20/05/2016 18:09, Max Ivanov wrote: >> >> so it uses "zero word" and "null word" interchangeably, which doesn't >> help either :) "zero word" seems closer to "empty word" (==no >>

Re: backtick to NOT set variable

2016-05-18 Thread Max Ivanov
> > Not if it succeeds. > However, backtick -i will exit on error: you can use that difference in > program flow to create the sequence you need. I didn't find a construct where rest of the program can be executed in same process as `backtick`, or at least forked after `backtick`. Closest I