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

2.5 "How to deal with input piped to ss" #16

Closed
kartva opened this issue Sep 24, 2020 · 3 comments
Closed

2.5 "How to deal with input piped to ss" #16

kartva opened this issue Sep 24, 2020 · 3 comments

Comments

@kartva
Copy link

kartva commented Sep 24, 2020

TODO still points to old github page, which now leads to a 404.

image

Link

@michelk
Copy link

michelk commented Jun 11, 2021

It would be great to have an example cli-program with usage:

sample-program --output <optional-output-file> <optional-input-file>

if --output is missing, output will be written to stdout; if input-file is missing, input is read from stdin.

Thanks.

@michelk
Copy link

michelk commented Jun 11, 2021

The above mentioned feature-request should go into section 1.2. Therefor I opened a new issue #36

@kartva
Copy link
Author

kartva commented Jun 25, 2021

Closing in favor of #36

@kartva kartva closed this as completed Jun 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants