Re: --nest for nested argument files

[Hans Schou]

On Thu, 5 May 2011, Ole Tange wrote:

> On Tue, May 3, 2011 at 6:08 PM, Ole Tange <tange@gnu.org> wrote:
> > On Tue, May 3, 2011 at 4:25 PM, Hans Schou <chlor@schou.dk> wrote:
> > > 2011/5/3 Ole Tange <tange@gnu.org>:
> >
> > > > Do you have a better idea for the syntax? Should it be default (and
> > > > thus the current behaviour would require you to use --xapply)?
> > >
> > > I thought --nest was default. I suggest that --keeporder is changed to
> > > be the one to use if you want to run line by line.
> >
> > If no one is using the current xapply-like functionality (I think I
> > have used it once) then I will change the default to nesting and make
> > the current behaviour available using --xapply.
>
> For all you alpha-testers: The git version now can do:
>
> $ parallel echo {1} {2} {3} :::: <(seq 1 3) <(seq 4 5) <(seq 6 7)

Could you just reverse the order of --arg-file's ?

$ src/parallel echo {3} {2} {1} :::: <(seq 6 7) <(seq 4 5) <(seq 1 3)
Name "main::opt_xapply" used only once: possible typo at src/parallel 
line 360.
1 4 6
1 4 7
1 5 6
1 5 7
2 4 6
2 5 6
2 4 7
2 5 7
3 4 6
3 5 6
3 4 7
3 5 7

I mean, you make a change, and then I can write:
  ... :::: <(seq 1 3) <(seq 4 5) <(seq 6 7)
and get the output above?

(was that understandable?)

/hans
--
Horsebakken 78, DK-2400 København NV