Skip to content
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

Future of pipes #30

Open
hongaar opened this issue Dec 1, 2019 · 1 comment
Open

Future of pipes #30

hongaar opened this issue Dec 1, 2019 · 1 comment
Labels
Question ❓ Further information is requested
Projects

Comments

@hongaar
Copy link
Member

hongaar commented Dec 1, 2019

Similar to #29, but for piping. This is actually a more common feature of Vorpal, and mentioned and demoed on the wiki/website. But like sessions, it does add quite a lot of noise to the source code currently, and I wonder how many use cases there actually are for this feature.

The obvious alternative for this feature is core shell piping functionality.

If we decide to keep it in the Vorpal code, it'd be a good candidate to be refactored.

@AdrieanKhisbe AdrieanKhisbe added the Question ❓ Further information is requested label Dec 4, 2019
@AdrieanKhisbe
Copy link
Member

To me it doesn't really compare to sessions, as they dont need a extra package to work.
(so we can have no idea of how much this is used)

Beside, I can't even consider some cli interpreter like bash not having piping feature.

But sure, it won't suffer a (potentialy massive) refactor :)

@AdrieanKhisbe AdrieanKhisbe added this to To do in reforge via automation Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question ❓ Further information is requested
Projects
reforge
  
To do
Development

No branches or pull requests

2 participants