Forward stdin when terminal is a TTY

[desbma]

When using right.backend.auth.cmd to get password from a program that itselfs prompts a password (ie. keepassxc-cli to unlock a database), there is absolutely no UI feedback, so neverest appears to be frozen, when the subprocess is just waiting for a password input.

Setting right.backend.auth.cmd = "echo 'Enter password> ' && keepassxc-cli ..." as a workaround does not work either, because the process stdout is captured by neverest.

[soywod]

there is absolutely no UI feedback

Indeed, stdin is not forwarded when spawning commands. Commands are responsible for prompting their own input. For example, when running GPG commands, people should use the right flavour of pinentry (GTK, QT…).

That said, Neverest could check if the current terminal is a TTY:

• If so, then it can forward stdin to send input to commands
• If not, keep the actual behaviour (do not forward stdin)

[desbma]

That said, Neverest could check if the current terminal is a TTY:

* If so, then it can forward stdin to send input to commands

* If not, keep the actual behaviour (do not forward stdin)

Sounds good to me.

Another nice addition would be to output a message like Getting password with command XXX..., that way the user would now Neverest is waiting for a subprocess. This is the root issue in my opinion, when I added --debug, I immediately understood what was going on.

[soywod]

Another nice addition would be to output a message like Getting password with command XXX..., that way the user would now Neverest is waiting for a subprocess. This is the root issue in my opinion, when I added --debug, I immediately understood what was going on.

I am not convinced about a message, I believe logs are fine. They should be used exactly the way you did: when you have a problem and try to dig. Otherwise I am afraid such messages will disturb the whole experience.

Let's keep this issue open for the stdin forwarding. Thank you for your feedback!