-
Notifications
You must be signed in to change notification settings - Fork 25
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
Provide input via stdin and as an argument #128
Comments
won't be implemented for now |
What was the motivation for not merging this feature? I was experimenting with sgpt recently and this was one of the first things I wanted to do. Specifically:
I would have liked sgpt to send two messages to the chat, one with the piped file, and the second with the command-line prompt. |
Good question. At that time, this would have meant that I had to introduce another breaking change which meant a new major release - which I was not willing to do. The software was supposed to be more stable. |
Yes, it's fine to have a second argument for me (so like The current workaround doesn't work for me; it's not ergonomic. My "current workaround" is to use llm instead when I want to do this ( |
Thank you very much for your input! I will reopen this issue and integrate it. I cannot give you a timeline right now, but I will try to do it in a timely manner. |
Is your feature request related to a problem? Please describe.
Sometimes I want to pipe in some data (e.g. a file) and provide a prompt, what to do with the provided input via stdin.
Describe the solution you'd like
I want to be able to provide input via stdin and as an argument.
The input via an argument should be appended in such cases.
Example:
cat some-file | sgpt "my prompt what i want to do with this file"
Describe alternatives you've considered
You can concatinate input in bash by using parentheses (see example below), but this solution is rather complicated.
( cat some-file; echo "my prompt what i want to do with this file"; ) | sgpt
Search
Code of Conduct
Additional context
No response
The text was updated successfully, but these errors were encountered: