4 ms·
I echo the author's feelings, though not for the same reasons. The main reason I want to be comfortable if not proficient in vim - and why I use it as my goto e
by hiyer 2y ago
I echo the author's feelings, though not for the same reasons. The main reason I want to be comfortable if not proficient in vim - and why I use it as my goto editor - is so that I know my way around when I have to login to remote servers.
But with my neovim setup now relying on Telescope, Ack, and various other plugins, it takes me a minute to get my bearings when I have to work without them on remote servers.
- drio 2y agoI can totally relate to this. My approach depends on how often I'll be working on the server. For quick, one-off tasks, I stick with the system's plain vim distribution. However, if it's a machine I'll be accessing frequently, I go ahead and set up neovim with my config files. The setup process can be tricky, as you mentioned. My config relies on several external dependencies, particularly for LSP servers. I usually ignore the dependency errors initially unless I know I'll need those specific features – then I'll invest the time to fix them properly. Installing neovim itself can also be challenging, especially on fixed/point release operating systems. I've found using AppImage to be the most reliable solution in these cases. I'm curious to hear how others handle this balance between convenience and functionality on remote servers.