Vim was developed by Brian Moolenaar as an improvement upon vi. You may even know it by its inspiration, vi, the text editor written by Bill Joy in 1976. If you have experience with any form of UNIX (Linux, FreeBSD, Solaris, etc.), then you undoubtedly have used, or at least heard of, Vim. If you want to check out all my different configuration files for zsh, Alacritty, as well as Neovim, take a look at this GitHub repository albingroen/.A Blast from the Past Here's what my configuration for Neovim looks like right now: " Start plugin managemer For example, if I'm working on a React.js project, I have one instance where I run the server, and then one where I run Vim and edit the code. Instead, I run several instances of Alacritty. I find that when using Tmux the editing performance inside of Vim is slightly worsened, and makes me focus more on which window, session, or pane I'm at all the time instead of focusing on writing the actual code. A couple of extensions that I find really necessary are coc.nvim, for intellisense, and vim-just-pretty and yats.vim to get React/Typescript syntax highlighting. I've tried to keep my Neovim configuration fairly simple, although not by compromising the editing experience. This created a very nice terminal experience, which for me works better than iTerm.
It makes sure to add some padding to the window, changes the font family and ups the font size, as well as fixes a couple of annoyances that come with Alacritty. The configuration, as you can see, is fairly simple. # Reload Alacritty if the configuration changes # Number of lines the viewport will move for every line scrolled when
# Maximum number of lines in the scrollback buffer. Here's what my configuration for Alacritty looks like right now: import: It's also very customizable, which is nice. Alacritty is a far more low-level terminal emulator but does take home the performance price in my experience. Don't get me wrong, iTerm is a really great terminal, that has features like tabs and splits, that Alacritty lacks. When it comes to the terminal, my experience is that the performance of running Vim in the terminal is far better in Alacritty, than say in something like iTerm2. Here are the 3 components that make up my setup: This will probably be changed in a couple of weeks though, or I might as well have gone back to VScode. Now I think I have a pretty decent setup though, and I thought I'd share it with the world. Mostly because of the lack of auto-completion, worse performance, or modernity of Vim. Every time I've tried using Vim for a substantial amount of time, I always found myself longing back to Visual Studio Code.
0 kommentar(er)
