Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Neovim 0.7 Released

github.com

Post reply on HN
Print view View original

171–180 of 220 posts

Re: Neovim 0.7 Released

#171

Post by recuter »

capableweb wrote: post #157
ufo wrote: post #115

Earlier quoted context omitted.

It's not too bad, because the most basic commands are about the same. The ones that get me the most are dd and V. When I switch to the other editor I get these wrong a couple of times before the mental model readjusts. That said, I never was a super advanced vim user because I couldn't remember the rarely used motions. Part of the reason I started using kakoune is that I find it easier on my brain. Basically everythi…

I've been using vim (neovim) for more years than I can count, but there is still so many movements that doesn't stick in my head, probably because I don't use them so much. I recently came across the which-key.nvim ( https://github.com/folke/which-key.nvim ) neovim plugin, which helped me a lot to speed up finding what movement I want to do. It basically shows you a popup with what combinations are possible after you…

This is neat. I'm the type that immediately disabled the arrow keys when I was learning vim and treated it like learning the piano (which, I admit, is a bit mental) and just forcefully drilled most of it into muscle memory.

I think this would have sped me up even more. Definietly neat. There's also a few plugins/configs around highlight as-you-search worth exploring. That being said I strongly recommend against going plugin shopping, you only need precious few. It is a better use of your time to do it the hard way sometimes.

Re: Neovim 0.7 Released

#172

Post by recuter »

davidkunz wrote: post #58
OtomotO wrote: post #54

I think Helix does a lot right on the "initial configuration" front. It comes with LSP and treesitter configured out of the box. Neovim on the other hand is heavily customizable, but you also have to do this for awesome functionality

For people interested in Helix, I've done a small video: https://youtu.be/9Zj-wiQ9_Xw

This is a well done video and Helix is cute. But I feel like this is more of an Emacs-y batteries included attitude and therefore blasphemy.

Configuring Neovim from scratch is part of the fun of learning your editor and isn't that much work.

Re: Neovim 0.7 Released

#173

Post by ilovecaching »

ylyn wrote: post #162
ilovecaching wrote: post #3

I will never understand why people choose VSCode/Jetbrains over a terminal based editor. I can edit the kernel with clangd and get hover reference, autocomplete, go to def, ref, dec, smart refactor, and that's on top of being able to easily jump and fix lint/bugs using Vim's already great support for parsing compiler errors. With term added (which is a core Vim feature) it also has excellent support for gdb debugging…

> I can use my editor over ssh and edit anywhere, I don't need a GUI to even be installed on the system where I have all of my cores and RAM for compiling the kernel, I can use VS Code in the browser: https://github.com/coder/code-server > it starts up instantly, I launch my editor once a day. Why do you need to keep killing and starting your editor? > and it's completely free and open source, OK, so is VS Code, or a…

Linux newbies jumping into Microsoft's arms is still something I'm trying to wrap my head around.

Re: Neovim 0.7 Released

#174

Post by _blz2 »

totetsu wrote: post #64

Does 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)

I use neovim on centos. Usually build it myself, but I used to grap app image earlier, just do wget here:

https://github.com/neovim/neovim/archive/refs/tags/v0.7.0.ta...

and untar into a local ~/usr/local directory that I maintain myself.

Compiling is neovim at work is a hassle, since its dependencies are from sites which are behind a firewall. So I decided to use locally built dependencies. The most painful part was getting the 3 luarocks 5.1 (which is not the latest) packages to compile locally and work with neovim.

Re: Neovim 0.7 Released

#175

Post by tekknolagi »

scottlamb wrote: post #165
ComputerGuru wrote: post #160

Earlier quoted context omitted.

I'm not sure if I understand you, but with EDITOR=nvim it'll do just that. To "commit" w/ the message you have in editor, ZZ. To abort, use :cq

That's a separate nvim instance within the terminal of the outer nvim instance. If I'm understanding this feature correctly, the idea is that instead of that, you make the outer nvim instance do stuff. Then pasting back and forth between buffers works better, etc. It wasn't clear to me from this short blurb though if that includes blocking for the buffer to be handled and then signalling success or failure to the cal…

It would be nice if it overrode EDITOR with some command that opened a new pane in your existing Nvim session. That seems doable.

Alternatively, Tim Pope's fugitive is pretty great and you can write :Git commit and it does just that.

Re: Neovim 0.7 Released

#176

Post by elpatoisthebest »

DavidWoof wrote: post #136
elpatoisthebest wrote: post #74

Earlier quoted context omitted.

The 100% full reason for me was that I had a job where I needed to SSH into our prod server about once per month and tweak some files. I was so terrified every time I had to do it because I was afraid of vim and/or nano in those situations. So I decided to get competent so I trusted myself not to make huge mistakes. After about a week of using vim it clicked and I knew I couldn't go back to Sublime Text. As for VS Co…

> The 100% full reason for me was that I had a job where I needed to SSH into our prod server Statements like this are common, but they confuse two usages: (a) learning vi/vim well enough in order to use it in any unix environment vs. (b) using vim with a complete plugin/config suite as a primary development IDE replacement tool. The former is IMHO an essential unix skill, but it's incredibly inefficient to try to us…

That's a totally fair point, and I realize my comment wasn't really in the spirit of that original thread in the first place.

What I really meant to convey is that I dipped my toes in just enough to get familiar, and that was enough for me to get fully hooked on vim. I've spent lots of time trying to make Jetbrains/IdeaVim and VSCode/vim-plugin work for how I write code. Significantly more than I want to admit publicly...but I come back to the boring old terminal every time.

I am not trying to convince any person on this planet that they should use vim. In fact, when other developers at work ask me if they should try I say "No" 100% of the time. But Jetbrains/VSCode are a firm step down for my workflow.

Re: Neovim 0.7 Released

#177

Post by kldx »

lazyier wrote: post #137
ilovecaching wrote: post #3

I will never understand why people choose VSCode/Jetbrains over a terminal based editor. I can edit the kernel with clangd and get hover reference, autocomplete, go to def, ref, dec, smart refactor, and that's on top of being able to easily jump and fix lint/bugs using Vim's already great support for parsing compiler errors. With term added (which is a core Vim feature) it also has excellent support for gdb debugging…

I don't know why people would use a text editor in a terminal when they can use that same text editor as a desktop application. Fonts are better, colors are better, it is faster, less latency, running a terminal inside your editor works better, pop-ups and overlays work better/are more flexible/easier to read, mouse interactions work better, resizing works better, it is easier to run multiple windows, it is easy to r…

Thank you, I agree with this perspective. The content density from a professional IDE is higher than what I get from a terminal editor. I can't imagine tooltips using the same font size as the rest of my code. I don't like it when the UI elements use monospace fonts.

Re: Neovim 0.7 Released

#178

Post by lawn »

xboxnolifes wrote: post #100
lawn wrote: post #77

Earlier quoted context omitted.

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.

> 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 thing 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 surpa…

I mean, it's kind of expected to forget about them if you took a break for a year after having used it for 6 months?

I do think 6 months should be enough to see some benefit in your workflow (like ci" to delete everything between "" and go into insert mode or Ctrl-O to go back to the last place you jumped from).

But I guess it depends on how you practiced, and if you look at those 6 months I'm sure you'll see that the time spent on actually learning Vim (struggling to learn these efficient editing patterns) was much less than you'd think.

With a tool like Vim I don't think it's enough to just use it, but we need to put conscious effort into it to learn it properly.

Re: Neovim 0.7 Released

#179

Post by oblio »

colordrops wrote: post #78
blowski wrote: post #5

Earlier 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…

It's much more than 1% though.

That's a claim no real study ever has measured to any truly scientific degree.

So it's just a claim.

Re: Neovim 0.7 Released

#180

Post by oblio »

xigoi wrote: post #149
zorr wrote: post #70

Earlier quoted context omitted.

I'm a dev that spends 90% of his computer time with a JB IDE open and I'll give you my perspective on it. It just works out of the box (or with a couple of 1-click install plugins) for practically all my use cases. * I mostly write Kotlin/Java for backend, desktop and Android projects. JB has that covered: Gradle integration, refactoring, navigation, dependency updates, documentation viewer, visual git log/diff/merge…

You're paying about a minute every time you have to wait for your IDE to start. That quickly adds up.

I've had systems were the IDE starts up after the OS boots and the OS is only shut down for security upgrades every few months.

Different workflows.

Post reply on HN