4 ms·
Vim works great. Don't see why you'd want to use anything else, except maybe Emacs.
by techntoke 6y ago
Vim works great. Don't see why you'd want to use anything else, except maybe Emacs.
- rhabarba 6y agoI am quite happy with (Acme and) GNU Emacs as my GUI editors, but Emacs is really annoying to use on a console to me, especially on non-native platforms like Windows. One of the reasons why I like the article.
- techntoke 6y agoUntil recently with Windows Terminal the Windows console app has been garbage. Any text editor would suck using the classic Windows console.
- rhabarba 6y agoI find the Windows Terminal much inferior to ConEmu. Anyway, text editors specifically written for DOS environments integrate rather well with the „classic Windows console“.
- yellowapple 6y agoThankfully, you don't have to use Emacs on the console. Not even on a Powershell-only Windows system (such systems will let you launch graphical applications just fine). Even in the article's use-case (remotely editing files on some remote server), Emacs ships with TRAMP, which can be used with PuTTY's plink to do remote editing (assuming the remote host is accessible via SSH): https://www.emacswiki.org/emacs/Tramp_on_Windows https://www.emacswiki.org/emacs/Tramp_on_Windows There's also support for TRAMP over SMB, though I haven't personally tried it (usually for SMB I let the OS handle it and then point Emacs at the local representation).