Force stdin when grepping piped data #53
Open
Conversation
This file contains 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
According to the grep man page: If no FILE is given, recursive searches examine the working directory, and nonrecursive searches read standard input. In the case of gf, most patterns usually use the recursive flag which will prevent gf to work as expected when piping data to it. This commit fixes this behavior, forcing grep to process stdin even when the recursive flag is used.
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.
According to the grep man page: If no FILE is given, recursive searches examine the working directory, and nonrecursive searches read standard input.
In the case of gf, most patterns usually use the recursive flag which will prevent gf to work as expected when piping data to it. This commit fixes this behavior, forcing grep to process stdin even when the recursive flag is used.