You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the Stdin module should read from /dev/tty instead of stdin (or else the user should be able to choose). Otherwise writing interactive programs that read input from stdin (e.g. fzf in cat ... | fzf) will have problems.
Specifically, when I tried doing that with minttea, I got an ENOTTY error message (although the program still seemed to function as expected). Changing the stdin module to start with let stdin_fd = Unix.descr_of_in_channel (In_channel.open_bin "/dev/tty") got rid of it.
The text was updated successfully, but these errors were encountered:
Hi @roddyyaga! This makes perfect sense. Also would be kinda cool to "replay" by going cat file | tui. Should I make the change or would you prefer opening a PR?
I think the Stdin module should read from
/dev/tty
instead of stdin (or else the user should be able to choose). Otherwise writing interactive programs that read input from stdin (e.g. fzf incat ... | fzf
) will have problems.Specifically, when I tried doing that with minttea, I got an ENOTTY error message (although the program still seemed to function as expected). Changing the stdin module to start with
let stdin_fd = Unix.descr_of_in_channel (In_channel.open_bin "/dev/tty")
got rid of it.The text was updated successfully, but these errors were encountered: