Live data from Hacker News

Neovim v0.4.0

github.com

141–150 of 168 posts

Re: Neovim v0.4.0

#142
post #133

Earlier quoted context omitted.

The option to use proportional fonts is a very rare feature in vim-like text editors (the only other way I know of is to use terminal vim in mlterm), so for people who want this the screenshot is good advertisement. In fact, after reading you comment, I promptly startet to install it (still compiling as I type this). My use-case is creative writing: I'm very used to vim keybindings from coding, but prefer to have a v…

fvim author here. The font in the screenshot is `Iosevka Slab` which _is_ monospace -- `fvim` currently syncs with the neovim grid system and doesn't support proportional fonts well. Sorry about the confusion -- I think you've already discovered that (after 46 minutes)!

Wow, I was completely fooled by the serifs and my excitement. Thank you for clearing that up!

Re: Neovim v0.4.0

#143
post #96

Earlier quoted context omitted.

Because Vim modes usually don't support more than a handful of basic features, let alone plugins and custom keybindings. Vim also starts up without any noticable delay and can be used for every text file, no matter in what context.

>Vim also starts up without any noticable delay Only if you run it without any plugins. Unfortunately if you have a lot of third party packages, vim startup times start to get closer to emacs startup times (both of which are still better than any IDE I have used, of course). I keep a vim.norc alias in my alias file which launches vim with an empty .vimrc for this very reason.

You could use autocmd for filetypes that require plugins, so they don’t load for configs/texts. If your pm of choice allows this separation, ofc.

I’m not very experienced with complex plugins, but most of what I’ve seen did nothing unless explicitly initiated. Maybe there are global variables to control that.

Re: Neovim v0.4.0

#144
post #133

Earlier quoted context omitted.

The option to use proportional fonts is a very rare feature in vim-like text editors (the only other way I know of is to use terminal vim in mlterm), so for people who want this the screenshot is good advertisement. In fact, after reading you comment, I promptly startet to install it (still compiling as I type this). My use-case is creative writing: I'm very used to vim keybindings from coding, but prefer to have a v…

fvim author here. The font in the screenshot is `Iosevka Slab` which _is_ monospace -- `fvim` currently syncs with the neovim grid system and doesn't support proportional fonts well. Sorry about the confusion -- I think you've already discovered that (after 46 minutes)!

>The font in the screenshot is `Iosevka Slab` which _is_ monospace -- `fvim` currently syncs with the neovim grid system and doesn't support proportional fonts well.

Aha, looked like a proportional font was used to me. I'd use a more well designed monospace font for the first impression!

Re: Neovim v0.4.0

#145

Here's a random question for Vim users who might know Kakoune... What can be done to make Vim behave like Kakoune? Odd question, I know. As a former Vim user, I switched to Kakoune about a year ago and absolutely love it. The multi cursor behavior, and selection before action combined to make a really excellent and visual experience. With that said, after 15 years in the Terminal, I tire of it. I want a GUI. Neovim h…

Can you elaborate a bit further on why you prefer Kakoune over Vim ? Thanks.

So, I used Vim for years - but frankly I only used what I needed. I never played vim-golf extensively, so please don't take what I say as the reasons I enjoy Kakoune as evidence of shortcomings in Vim. With that said:

Kakoune's multi-cursor support sort of blew my mind when I first started using it. Combined with the always selection first model of Kakoune, it means you can plop down 10 cursors, navigate around, select, reduce and etc all of them separately will actively viewing what they have selected. Finally when you get all the selections you want, you can act on them. That's really my main workflow that I just have to have.

Plugins may perhaps solve my issue. We'll see. I also am not sure how realistic living entirely in visual mode in Vim is. I'm not too well versed in visual mode, so I can't speak on it too much.

Kakoune has really been a joy for me. I just want more advanced features that Terminals can't provide (multi fonts, more UI elements, etc)

Re: Neovim v0.4.0

#146
post #87
post #71

Earlier quoted context omitted.

The terminal is common to many operating systems and keyboard shortcuts leant there are pretty universal. If you prefer a keyboard driven workflow learning to use a terminal and terminal based editor will give you a very portable solution. Vi's commands are somewhat like a language for manipulating text. This is a different philosophy to many non-modal editors. In vi you can say change the next 3 paragraphs to foo or…

I guess it depends on the usecase. You mention a lot of scripting, and also the terminal. Would you also recommend vim for working on large projects with 100+ files? I believe in this case, a full on IDE is suited better. Also I'm not so sure about the portability. Sure, some of the knowledge is reusable, but when all the vim installations are not "batteries included", every installation will be configured differentl…

> Would you also recommend vim for working on large projects with 100+ files? I believe in this case, a full on IDE is suited better.

I do that now.

IMO, it depends on the language. For C#, nothing beats Visual Studio. For all of its warts, the autocomplete, go-to-def, and debugging just work too well. I do use a Vim plugin in it. It's missing some features that full Vim has, but the other advantages make up for it.

For Ruby, Python, etc, I think pure Vim wins, including with large projects. I know it's possible to get autocomplete support in Vim, but never found it to be worth the trouble for those languages. No issue in handling a bunch of files with Nerdtree and CtrlP. I think the terminal is better for actually running the program and related tasks than any IDE environment I've tried. Especially with Tmux to spin up new windows easily and switch between them, all without ever leaving the keyboard.

It is true that vim installs tend to be highly configured. IME, the bone-stock Vim on servers is easy enough to live with for the purpose of editing a couple of config files. Wouldn't be thrilled to use it on a large project though.

Re: Neovim v0.4.0

#147
post #12

What are the most notable improvements over vim that the authors of neovim speak of? https://neovim.io

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?

Re: Neovim v0.4.0

#148
post #21

I'll just leave a shameless plug for my neovim GUI project here: https://github.com/vhakulinen/gnvim . It has a WIP PR[1] for implementing multigrid support, which would allow features such as scrollbars. There are many other GUIs too, such as oni/oni2, gonvim, neovim-gtk and neovim-qt. Extensive list can be found here: https://github.com/neovim/neovim/wiki/Related-projects#gui 1: https://github.com/vhakulinen/gnvim/…

I'm using vimr [1] and never had issues with it 1: https://github.com/qvacua/vimr

Holy cow, that is pretty. I wonder which is better, Gnvim or Vimr for a full Neovim experience?

Either way, VimR is impressively nice looking. Thanks for the link!

Re: Neovim v0.4.0

#149

I'll just leave a shameless plug for my neovim GUI project here: https://github.com/vhakulinen/gnvim . It has a WIP PR[1] for implementing multigrid support, which would allow features such as scrollbars. There are many other GUIs too, such as oni/oni2, gonvim, neovim-gtk and neovim-qt. Extensive list can be found here: https://github.com/neovim/neovim/wiki/Related-projects#gui 1: https://github.com/vhakulinen/gnvim/…

Any advantages of using this vs the neovim in the terminal?

Re: Neovim v0.4.0

#150
post #30

Earlier quoted context omitted.

Are there any good alternatives for coc.vim? I do not like the NodeJS dependency.

I have been using LanguageClient-neovim[0]. It is great, the main difference I have observed between LanguageClient-neovim and coc.vim is that LanguageClient-neovim provides a more vim centered UX (e.g. it automatically populates location/quickfix list with errors, warnings and hints which enables quickly jumping between error locations) while coc.vim provides a great out-of-the box experience but feels like VSCode s…

Thank you for the elaborate answer, seems like LanguageClient-neovim will be a perfect fit!
Post reply on HN