And this release is the first one which is being continuously tested on OpenBSD with builds.sr.ht :) https://github.com/neovim/neovim/tree/master/.builds Welcome to the platform!
Awesome!
Neovim v0.4.0
161–168 of 168 posts
Re: Neovim v0.4.0
#162Earlier quoted context omitted.
Command line vim is one of the most productive editing environments on the planet, why wouldn't we?
I'd say language support is the most important for productivity if we talk about programming. Having the whole API under your fingertips, doing safe refactorings easily, etc. are much more important for productivity than simple editing. If you can refactor a class, move functions, rename variables across the whole project safely (string replace is not enough) with a few clicks then you are much faster than when you h…
In terms of what's been available for developers I'd agree with you that IDE's (especially JetBrains and especially for languages like Java) have had an advantage for some time. Language Server Protocol is taking this advantage away. It's not as if turning code into AST and transforming tree data structures is out of the reach :P.
Re: Neovim v0.4.0
#163Earlier quoted context omitted.
The most notable for all Vim users is probably forcing upstream vim to merge async support for plugins after refusing it initially; albeit with a different API. (there is quite some bitterness on both sides of this issue, I think) The other big win is providing a embedding API so other editors can be built on top of the core editing engine. Which resulted in multiple interesting GUI projects which you can find in oth…
What does "async support for plugins" mean when hands are on the keyboard? Linters/etc that run without a need for :w?
> Linters/etc that run without a need for :w?
That's more to do with how you setup to trigger the commands.
Async here really means that it doesn't block with your typing, jumping around in the text editor if plugin starts doing some heavy work in the background due to some action that got triggered by whatever event you had setup for plugin to do. One of the plugin that I particularly remember was syntastic (I haven't kept up with it to know if they've fixed this or not) that would just create janks every now and then if the workload was heavy.
Re: Neovim v0.4.0
#164Earlier quoted context omitted.
> Otherwise it is pretty much a drop-in replacement without issues. Except for the crashes. The crashes are an issue. Don't get me wrong though, I like nvim. I use it occasionally. But the crashes are an issue.
No crashes here and I use it all day pretty much every day. They only real negative in my view is the startup time which is noticeably worse than vim for me. Advantages I see are - unix clipboard and middle mouse pasteboard both work out of the box without having to recompile (ie "*p and "+p and the corresponding yanks just work) whereas on vim for whatever reason I always have to rebuild my distro vim and faff about…
> They only real negative in my view is the startup time which is noticeably worse than vim for me.
Check that this is not e.g. due to Python host detection/setup - you might have plugins that trigger both py2/py3 hosts to load for example. (hosts can be configured explicitly to skip it) Also check `nvim --startuptime /tmp/nvimlog`.
Re: Neovim v0.4.0
#165Earlier quoted context omitted.
OSX. Plugins: ale, bufexplorer, nerdtree, rust.vim, vim-airline, vim-airline-themes, vim-colors-solarized I generally start vim in my src folder on Monday and exit it on Friday. Occasionally, just on a whim, I run nvim instead. Mostly its fine. But the times I've experienced crashes or other hickups like rendering bugs forcing me to :qa!, it's been on nvim. Edit: Oh and I run it in the terminal, iTerm2 to be precise.
I wonder if any 2-4 of the folks who’ve never had it crash would find it fun to join in a mob-debugging session where you screenshare, we all open an discord* channel, and we try and figure out the cause and solution. —— (* IM could be discord, gitter, slack, or whatever. I’d argue strongly against IRC because I think the lack of support for code blocks and especially newlines makes it harder to talk about code/stack…
You can just try with reporting them as an issue on GitHub.. :)
Re: Neovim v0.4.0
#166On this topic, can anyone share their Python setup for Neovim? I used ALE and Deoplete + a bit of Jedi and got frustrated with it breaking / working much worse than ST3 and just removed all the plugins.
I use CoC.vim [0] with whatever Python plugin they recommend and it's easily been the most painless autocompletion I've ever used in over a decade of Vim. I wrote some (admittedly pretty basic) Python with it last week with no complaints! [0] - https://github.com/neoclide/coc.nvim
The python plugin that is recommended has switched from `pyls` to the Microsoft Python
Language Server (the same one that powers the Visual Studio Code Python extension),
written in C#. The extension comes bundled with a .NET Core interpreter.
Re: Neovim v0.4.0
#167Why do we need such things in 2019?
Because we haven't come up with anything better. Neovim, Vim, or Emacs combined with
Unix make a better IDE than an IDE.
With a fuzzy finder, Neovim start up in milliseconds and can scale to projects with several thousand files, complete with documentation, symbols, reference jumping, and refactoring. An IDE just turns my laptop into a space heater with minimal configurability and fewer features. In other words, I am investing more battery life for a weaker program. If I need to use someone else's computer (or a container), I can run Vim with my config file right in the terminal and never notice the difference.
The features I need:
1. FOSS
2. A reasonable amount of battery, CPU, and memory usage. The editor should not bring a browser/JVM with it. Browsers eat RAM and need to be restarted within a couple days of uptime, and the JVM kills the battery.
3. Cross-platform; should work on Linux and BSD.
4. Should scale to large projects with thousands of files.
5. Should support advanced features with something like the Language Server Protocol.
6. Minimal UI and keyboard-driven; screen space is often limited, and I hate the mouse with a passion.
Vim and Emacs are the only editors I have ever used that have all of the above features. Nothing else comes close.
Re: Neovim v0.4.0
#168Earlier quoted context omitted.
I agree completely. For me, for now, I have vscode with vim emulation. I find that it's more convenient to have everything vscode has + vim keys for a lot of things, than have all of vim + try to make vim do what I like from vscode. I really hope in the future I'll find the time to do that, but for now I am content. It's always a trade-off.
Have you noticed any sluggishness when using Vim commands in VS Code? I use nvim + tmux as my go to and it's pretty responsive (still has trouble catching up to me sometimes) but I often have to wait for VS Code.
I have to wait sometimes, but normally it's fast. It's only when (I think) somehow the vim emulation bugs out that I need to wait a couple of seconds or just hit esc 5 times. Thankfully it's not often.