Live data from Hacker News

How to Exit Vim

github.com

101–110 of 409 posts

Re: How to Exit Vim

#102
post #14

Oh looks, it's only been 10 minutes since the last Vim article was trending on HN, we're rivalling Hollywood levels of bubble here. Seriously, when CES is currently showing hundreds of new tech products and services, including a Hyundai electric helicopter - Vim is what we still talk about?

CES hasn’t been relevant in the past decade. Why would we care?

> CES hasn’t been relevant in the past decade. Why would we care?

And Vim is? When there are editors like VS Code?

Re: How to Exit Vim

#103
post #30
post #14

Oh looks, it's only been 10 minutes since the last Vim article was trending on HN, we're rivalling Hollywood levels of bubble here. Seriously, when CES is currently showing hundreds of new tech products and services, including a Hyundai electric helicopter - Vim is what we still talk about?

it's called hacker news, not electrical engineer news, not startups news

It's on YCombinator, which is a startup accelerator

Re: How to Exit Vim

#104
post #36

It's amazing to think how far we've come since June 2018 where the record was just shy of three minutes ( https://www.youtube.com/watch?v=TLbfqZBL8t8 ). These new strategies could allow experienced speedrunners to exit vim in times of 10 seconds (or perhaps less!?). I'm excited to see how this progresses, the vim speedrun community is vibrant and creative and I've no doubt we'll see a sub 5-second run within my lifet…

I believe the solution to this lies in using Rust and SIMD. It will achieve both performance and safety.

Re: How to Exit Vim

#109

Earlier quoted context omitted.

I live in a different universe to you it seems. The only vim command I know is :q . Honestly, I tried several times over the decades and walked away with my head buzzing. PS: I don't live in emacs either! What I do love in both camps is how the explanations begin... "All you have to do is...[insert irrational (to non-vim/emacs users) command]" which makes me laugh every time. Love the article, which ironically proves…

I know some basic commands and know it well enough to edit git commit messages and interactive rebase (`ddkP` is probably the most advanced command I know). But I've never thought "I prefer this over my regular editor this is amazing". I just don't get the satisfaction. And of course I'd have to dive deep into the ecosystem in order to get the same benefits that my main editor provides out of the box, like idk, cmd+c…

Mileage may vary depending on language support, but vim does have a go to definition feature[1][2]. I believe there is also out box error checking for some languages, and if that is not enough for you (and at the risk of offending a large number of vim purists), there is a fantastic plugin called ALE[3] that will likely provide you with what you want.

1: https://vimhelp.org/pattern.txt.html#gd

2: https://vimhelp.org/pattern.txt.html#gD

3: https://github.com/dense-analysis/ale

Re: How to Exit Vim

#110
post #104
post #36

It's amazing to think how far we've come since June 2018 where the record was just shy of three minutes ( https://www.youtube.com/watch?v=TLbfqZBL8t8 ). These new strategies could allow experienced speedrunners to exit vim in times of 10 seconds (or perhaps less!?). I'm excited to see how this progresses, the vim speedrun community is vibrant and creative and I've no doubt we'll see a sub 5-second run within my lifet…

I believe the solution to this lies in using Rust and SIMD. It will achieve both performance and safety.

I would prefer a functional approach and formal verification so we can know for sure it will exit.
Post reply on HN