diff options
| author | Konstantin K <Hi-Angel@yandex.ru> | 2025-01-11 19:01:46 +0300 |
|---|---|---|
| committer | Gabriele Bozzola <sbozzolator@gmail.com> | 2025-01-13 08:45:30 -0800 |
| commit | 056ad74653704bc353d8ec8ab52ac75267b7d373 (patch) | |
| tree | 421af756a03f3d13fe1c208aea8cad120d772558 | |
| parent | 99c1f5e76ac927825775c887c93e46036fac7327 (diff) | |
README: link the issue of running on Windows
It seems there is demand for making this work on Windows, so would be nice if the text that says it doesn't work would be linked to the issue that contains the research. This will allow interested people *(if such appear)* to avoid researching everything from scratch, but rather basing their work on the information already done by others.
This came up on SE: https://emacs.stackexchange.com/questions/82896/error-use-package-vterm-catch-searching-for-program-no-such-file-or-direct/82909#82909
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -45,7 +45,7 @@ For the long answer, let us discuss the differences between `eshell`, `shell`, `vterm` outperforms `term` and has a nearly universal compatibility with terminal applications. -Vterm is not for you if you are using Windows, or if you cannot set up Emacs +Vterm is not for you [if you are using Windows](https://github.com/akermu/emacs-libvterm/issues/12), or if you cannot set up Emacs with support for modules. Otherwise, you should try vterm, as it provides a superior terminal experience in Emacs. |