I did a brief write up on some of the biggest new features here: https://gpanders.com/blog/whats-new-in-neovim-0-7/
Thanks for summarizing the highlights! The client-server part is the one I'm most excited about. It is one of my favorite things in kakoune and it'll be nice to have it on neovim too. I find it more intuitive to use separate terminal windows with all the usual window manager shortcuts, instead of using vim-specific terminal splits.
Neovim 0.7 Released
91–100 of 220 posts
Re: Neovim 0.7 Released
#92Re: Neovim 0.7 Released
#93Does any one have any advice for running neo vim on a centos host without admin to install it. (Short of hunting down all the source packages for dependencies and compiling)
Install it via nix, or if nix is too big a leap, via conda.
Re: Neovim 0.7 Released
#94I did a brief write up on some of the biggest new features here: https://gpanders.com/blog/whats-new-in-neovim-0-7/
Does the new filetype.lua script still run the ftdetect/ scripts? Or will those only be run by the filetype.vim fallback and need to be ported to the new system?
Re: Neovim 0.7 Released
#95Earlier quoted context omitted.
It's a weekend of learning for a tool that you use your entire life. Any computer scientist should realize the power of amortization.
I absolutely want to learn VIM but saying it's only a weekend is plain misinformation. We're definitely looking at months of gradually building new habits.
I'm a committed (neo)vim user, but I readily admit I only got over the hump because I thought it was cool and hardcore and typing is easy for me. There's no question it's been worth it for me, and I would argue it's probably worth it for most people and better for the software ecosystem as a whole (GUI tools don't compose), but still I think trying to say one's better than the other is too narrow a view.
Re: Neovim 0.7 Released
#96Earlier quoted context omitted.
Both vim and neovim have the ability to open a terminal in a window split. It's not my preferred workflow but some people really like it rather than tmux or ctel-z to drop onto a shell... the implementation of this feature in neovim is a lot nicer than the one in vim. One thing i do use it for: In neovim there's options to open the terminal as a sort of overlay on top of the existing splits, they call it floating ter…
Why wouldn't you set the makeprg and have it populate the quickfix list instead?
Re: Neovim 0.7 Released
#97> MessagePack structured communication enables extensions in any language
Is anyone writing extensions in other languages? Does it work well?
Re: Neovim 0.7 Released
#98Re: Neovim 0.7 Released
#99Example 1:
nvim .
Still uses Netrw, which is fine, but doesn't even attempt to do things like: let g:netrw_preview=1
let g:netrw_banner=0
let g:netrw_browse_split=4
let g:netrw_liststyle= 3
let g:netrw_altv=1
let g:netrw_winsize=8
So that you get something that remotely resembles a modern text editor's tree view.Example 2:
set number
Line numbers are off by default. Why? Why are all of these other configurations on by default? Every editor shows line numbers by default and Neovim doesn't make this 1 line configuration effort to look like everyone else.Example 3:
set mouse
Mouse is off by default. Again, why? I get that it's a terminal editor, but if the technology is there to allow me to select text with my mouse, why do we need act like luddites?After setting up my .vimrc file with sane defaults and a bit of an attempt to use the editor in earnest, my conclusion is that Vim/Neovim is just a bad editor.
I want more from my editors.
Here's a .vimrc file that attempts to make Vim and compatible editors more like Visual Studio Code, Atom, and Sublime Text:
https://github.com/andrewmcwatters/dotfiles/blob/main/.vimrc
And it's still bad.
Re: Neovim 0.7 Released
#100Earlier quoted context omitted.
> I will never understand why people choose VSCode/Jetbrains over a terminal based editor. I don't want to use my valuable time learning how to get vim working in some super-optimal way that's hypothetically going to improve my productivity by 1%. JetBrains consistently works well enough for me that I'm not going to bother switching. 90% of my life is spent thinking about how to solve the problem so the editor is not…
If you're a lifelong programmer the time it'll take to be proficient in Vim is a drop in the bucket in the grand scheme of things. A tool that can last a lifetime and be used for any programming language at that. It's just a trade-off between optimizing for the short-term or the long-term.
I just don't see it? I spent a good 6 months only using vim to see if I could get it to stick. Then I took a year break. After the break I forgot nearly every shortcut I was using minus a select few. I never got to the point of even matching my efficiency in other editors, let alone surpassing them.
6 months alone is already more than what I would consider worth in regards to time spent learning a tool for the little gain I see it bringing over just using intuitive, albeit less efficient, alternatives.