Take input files from stdin (standard input)#280
Merged
Conversation
|
For the case of reading from standard input, it is more common on Unix to use |
Contributor
Author
|
I used |
Member
|
Interesting discussion, but currently I'm leaning more to how it is implemented now, since |
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This extends upon #273 and #279.
I always missed this in par2cmdline and since the logic is already in place,
it would now be nice to use the error-case where
@is followed by nothingfor taking the input from standard input, arguably a common Linux use-case.
This would allow for setups like:
And especially use in shell-scripting feeding other command's output into par2cmdline.