-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
CLI can't be automated easily? #1221
Labels
Comments
An alternative which would keep the useful messages would be to add a |
lhark
pushed a commit
to lhark/keepassxc
that referenced
this issue
Jul 10, 2018
Writing the prompt to stderr greatly helps with the use of keepassxc-cli in automated scripts or as a password provider for programs like mutt or borg. This is done in accordance with POSIX that specifies that diagnostic messages be sent to stderr. This commit should be a first step in solving the following issues: keepassxreboot#831, keepassxreboot#1221
droidmonkey
pushed a commit
to lhark/keepassxc
that referenced
this issue
Sep 26, 2018
Writing the prompt to stderr greatly helps with the use of keepassxc-cli in automated scripts or as a password provider for programs like mutt or borg. This is done in accordance with POSIX that specifies that diagnostic messages be sent to stderr. This commit should be a first step in solving the following issues: keepassxreboot#831, keepassxreboot#1221
lhark
pushed a commit
to lhark/keepassxc
that referenced
this issue
Oct 21, 2018
Writing the prompt to stderr greatly helps with the use of keepassxc-cli in automated scripts or as a password provider for programs like mutt or borg. This is done in accordance with POSIX that specifies that diagnostic messages be sent to stderr. This commit should be a first step in solving the following issues: keepassxreboot#831, keepassxreboot#1221
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using the CLI, it prints unecessary info like
Insert password to lock ...
.Sure, that's very nice of you. But then again, automated scripts have to somehow filter out that output.
How about you either remove it, or print it to STDERR (so you can pipe that to /dev/null)?
The text was updated successfully, but these errors were encountered: