cs:usable_windows
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cs:usable_windows [2020/04/01 04:54] paolo_bolzoni |
cs:usable_windows [2020/04/01 05:01] (current) paolo_bolzoni little touch up in winpty |
||
|---|---|---|---|
| Line 42: | Line 42: | ||
| alias docker='MSYS2_ARG_CONV_EXCL="*" docker' | alias docker='MSYS2_ARG_CONV_EXCL="*" docker' | ||
| - | So that Msys2 won't mangle any path. | + | So that Msys2 won't mangle any path. |
| === TTY-sensible programs === | === TTY-sensible programs === | ||
| - | Few programs, like __nodejs__, have problems using Msys2. When you execute them the console seems to hang. It is caused because the expect stdout do be a TTY, in other words stdout must follow the terminal interface protocol. | + | Few programs, like __nodejs__, have problems using Msys2. When you execute them the console seems to hang. It happens because they expect the stdout do be a TTY, in other words stdout must follow the terminal interface protocol. |
| - | In Mysys2 shell, it is not the case: | + | The Mysys2 shell does not: |
| $ node -p -e 'Boolean(process.stdout.isTTY)' | $ node -p -e 'Boolean(process.stdout.isTTY)' | ||
| Line 54: | Line 54: | ||
| Fortunately there is a solution: the program **winpty** | Fortunately there is a solution: the program **winpty** | ||
| + | |||
| + | $ winpty node -p -e "Boolean(process.stdout.isTTY)" | ||
| + | true | ||
| + | |||
| + | Let us see in action: | ||
| $ node | $ node | ||
| Line 65: | Line 70: | ||
| Much better! **winpty** can be installed with pacman. | Much better! **winpty** can be installed with pacman. | ||
| - | |||
| ==== Admin access ==== | ==== Admin access ==== | ||
cs/usable_windows.1585716887.txt.gz ยท Last modified: 2020/04/01 04:54 by paolo_bolzoni
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
