You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Commands that work in the pipeline fit into one of three categories:
Commands that produce a stream (eg, ls)
Commands that filter a stream (eg, where type == "Directory")
Commands that consume the output of the pipeline (eg, autoview)
Commands are separated by the pipe symbol (|) to denote a pipeline flowing left to right.
And I had to think about streem.
You have a lot of things to do already, so no need to add any more ideas to
the stack; but I think if you get to think about streem again in the future (perhaps
one day), a shell that showcases what streem can do, or how it can be used,
may be useful, similar to what the rushell.sh example shows. (Others can do
the video; for example, for pry, someone else did a video + intro showcase.
But before the video the idea may have to be formalized in code that works,
if any useful idea can be extracted from the above link - so I just wanted to
make sure that this was known to you. Thanks!)
The text was updated successfully, but these errors were encountered:
Hello matz,
Sorry to misuse the issue tracker for this; please feel free to close it.
I just noticed:
https://www.nushell.sh/
When i was reading this part:
And I had to think about streem.
You have a lot of things to do already, so no need to add any more ideas to
the stack; but I think if you get to think about streem again in the future (perhaps
one day), a shell that showcases what streem can do, or how it can be used,
may be useful, similar to what the rushell.sh example shows. (Others can do
the video; for example, for pry, someone else did a video + intro showcase.
But before the video the idea may have to be formalized in code that works,
if any useful idea can be extracted from the above link - so I just wanted to
make sure that this was known to you. Thanks!)
The text was updated successfully, but these errors were encountered: