-
Notifications
You must be signed in to change notification settings - Fork 266
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
Unable to install fisher without a proper TTY #791
Comments
Probably related to: Line 23 in 2efd33c
I really like that ability, but maybe we should remove it for 4.x unless there's a way to have our cake and eat it too. Could you provide a simple script I can run to repro the issue? The code in your post is kind of unintelligible. |
Currently, I don't see any simple way to execute in nontty/non-pty environment other than using ssh -T (maybe using tool like cron ?) : If you have a local ssh server enabled, you can do this: ssh -T localhost "fish ./install_fish.fish" with install fish.fish file locally placed in you home dir: #!/bin/fish
set -l fish_trace on;
isatty && echo "on a tty, don't continue" && exit 43
curl -sL https://raw.githubusercontent.com/jorgebucaran/fisher/main/functions/fisher.fish | source && fisher install jorgebucaran/fishe I don't get the tty/pty stuff, but it's seems to be more related to unnexisting pseudo-terminal environment. The ssh documentation say:
|
After looking into this further, it seems like this might be a dupe of #742. I'll close here and leave a comment there instead. |
Hello all, thanks for this nice software. I'm using pyinfra tool and wanted to provision fish with fisher and few plugins directly.
I go very straightforward, using the "server.script" function of pyinfra to run a simple fish script that does the fisher installation, using the one-line method…
…and it goes not very well. The process just hangs infinitely there, without any useful information.
After digging a bit, i discovered that the script doesn't seem to handle correctly a non-tty interface. I can reproduce the issue with a simple ssh -T:
Is there any simple solution to this issue ?
Thanks.
The text was updated successfully, but these errors were encountered: