LIU Hao
[This whack-a-mole game](https://github.com/lhmouse/nano-win/commit/8ad1308195516595d8a531169bf260b8c859093a#diff-57b320cc7adea8a7d492648179ebdd206bb8090f0b897e8965b0b482d0dbc88bR45) isn't satisfactory, given the fact that paths in principle are very fragile (some of them come from environment variables such as `HOME`, some others are hardcoded such...
I should look into it later.
A new build has been uploaded at .
No. But wherever you do, make sure your '.nanorc' contains an absolute path to default syntax files.
Please try **MSYS2**'s **nano**. Keyboard inputs are handled by the native (i.e. not basing on any form of POSIX simulation) **ncurses** which does not conform to **POSIX**.
**nano-win** is not meant to be functional over SSH (note this is **ncurses**' limitation not **nano**'s). You should use **MSYS2**'s **nano** which can be installed via `pacman -S nano` and...
The reason why it doesn't over SSH is a bit complex but I'll try to elaborate a little: A **POSIX** terminal (such as the ones you get on a Linux...
Are you referencing the **MSYS2** **vim**?
> > * Where should I put all the `*.nanorc` files... > * ...and the `.nanorc`? Syntax files are loaded as specified in your primary `.nanorc` file. You may put...
@E3V3A The issue above works on Linux because the process receives `SIGWINCH` when the window is resized. This signal does not exist in Windows so I have to delete related...