Ability to redirect command output to a new file view #26
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
…g ">>" instead of ">" to the command
|
This is a good idea. In order to keep the symbols closer to their unix analogues it might make more sense to use |
Change of redirection symbols to keep close to unix usage : pipe redirects output to current view, right angle bracket redirects output to a new view.
|
I agree, and I have pushed a new commit to integrate this change. |
|
I merged this in with some cleanup. Thanks for your work! |
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.
By appending ">>" to the command instead of only ">", a new file view is created and output is redirected into it.