-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rethink r2 pipes #15435
Labels
Comments
XVilka
added
consoleui
enhancement
concept
Highly experimental features and controversial ideas
labels
Nov 8, 2019
We can implement the { command for this
… On 8 Nov 2019, at 06:29, Anton Kochkov ***@***.***> wrote:
Support more advanced ways of piping, a la PowerShell or https://blogs.gnome.org/alexl/2012/08/10/rethinking-the-shell-pipeline/. See also https://docs.microsoft.com/en-us/powershell/scripting/learn/understanding-the-powershell-pipeline?view=powershell-6
Idea is to pass JSON "objects" in some pipe cases without the hassle of handling them manually. We should make it a first-class citizen.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I propose a better one: |
Wat
… On 8 Nov 2019, at 09:26, Anton Kochkov ***@***.***> wrote:
I propose a better one: |>, not a problem with the upcoming proper parser anyway.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Nice-to-have feature, not a priority for me at the moment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Support more advanced ways of piping, a la PowerShell or https://blogs.gnome.org/alexl/2012/08/10/rethinking-the-shell-pipeline/. See also https://docs.microsoft.com/en-us/powershell/scripting/learn/understanding-the-powershell-pipeline?view=powershell-6
Idea is to pass JSON "objects" in some pipe cases without the hassle of handling them manually. We should make it a first-class citizen.
The text was updated successfully, but these errors were encountered: