4
DEVil666
37d

It’s me or Vim on Windows Terminal is barely usable?
I resorted to doubling my laptop’s ram (luckily Dell still produces laptop which can be upgraded and repaired with a set of common screwdrivers) in order to be able to install a FreeBSD VM in which I can finally get a decent terminal based development environment. Sadly since for my work I need a VPN which can run only on Windows and MacOS I cannot just remove Windows and switch to FreeBSD or Linux but I have to make a VM and route its network traffic through work VPN.

Comments
  • 2
    Have you tried WSL?
  • 1
    Why would you need a totally terminal based environment?
  • 1
    @iiii Because the Electron based VS Code can become lagging under stress and when I need to keep switching context for me is slow and annoying to do it over a GUI
  • 0
    @spongessuck yes and Cygwin too but they solves just half of the problems, Vim over Terminal keep being buggy with random color glitches and other annoyances
  • 2
    @iiii Cause its so freaking fast ? And i dont mean like it runs fast. But once you know CLI then GUI is just ultra slow to get things done. Heck i open terminal to create folders even at this point.
  • 1
    @Haxk20 sounds like some bullshit to me.
  • 1
    @DEVil666 tried neovim? Iirc, it has a windows build as well
  • 0
    @iiii thanks, I’ll try it but I don’t think it’s going to solve the problem since it isn’t caused by Vim but by Windows’s Terminal Emulator
  • 1
    @DEVil666 it's not running in a windows terminal.
  • 1
    @iiii to each one his own but I agree with @Haxk20, on most familiar tasks I’m faster on CLI especially if you take some time to configure your shell. For example I’m faster by testing an HTTP endpoint by writing “curl [something]” rather than locating the Postman executable, waiting for its startup (if closed), filling up the cumbersome GUI and hitting “send” in the end.
  • 0
    @iiii clear, is the same as GVim 👍
  • 0
    Running Vim on WSL via Windows Terminal works fine.
Add Comment