Skip to content
This repository has been archived by the owner on Jul 11, 2019. It is now read-only.

Change in behaviour of --max-args #44

Closed
jonasbb opened this issue Jan 23, 2017 · 2 comments
Closed

Change in behaviour of --max-args #44

jonasbb opened this issue Jan 23, 2017 · 2 comments

Comments

@jonasbb
Copy link

jonasbb commented Jan 23, 2017

In version 0.10 the upper first is seen, in version 0.11 the second one. I find the first one more useful and intuitive. From a quick look here, I could not find out why this was changed.

The old behaviour parses multiple args as individual arguments passed to the program, while the new behaviour passes it as a single long space-separated argument.

[0] bushart@Colossus07 ~/home $ parallel -n5 'cat {}' ::: 1 2 3 4 5
cat: 1: No such file or directory
cat: 2: No such file or directory
cat: 3: No such file or directory
cat: 4: No such file or directory
cat: 5: No such file or directory

[0] bushart@Colossus07 ~/home $ parallel -n5 'cat {}' ::: 1 2 3 4 5
cat: 1 2 3 4 5: No such file or directory
@jonasbb jonasbb changed the title Change in behaviour of '--max-args' Change in behaviour of --max-args Jan 23, 2017
@mmstick
Copy link
Owner

mmstick commented Jan 23, 2017

It shouldn't have changed, so I'll fix this later.

mmstick added a commit that referenced this issue Jan 23, 2017
- Resolves issue #44
@mmstick
Copy link
Owner

mmstick commented Jan 23, 2017

Latest change fixes this issue

@mmstick mmstick closed this as completed Jan 23, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants