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 Last revision Both sides next revision | ||
|
cs:usable_windows [2020/03/31 11:39] paolo_bolzoni Add a note about winpty |
cs:usable_windows [2020/04/01 04:58] paolo_bolzoni [Command line] |
||
|---|---|---|---|
| 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 to some TTY incompatibilities. Fortunately there is a solution: the program **winpty** | + | 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. |
| + | |||
| + | In Mysys2 shell, it is not the case: | ||
| + | |||
| + | $ node -p -e 'Boolean(process.stdout.isTTY)' | ||
| + | false | ||
| + | |||
| + | 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 58: | 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.txt · Last modified: 2020/04/01 05:01 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
