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

Neovim 0.5 is overpowering

crispgm.com

Post reply on HN
Print view View original

361–370 of 429 posts

Re: Neovim 0.5 is overpowering

#361

Post by MonaroVXR »

the_duke wrote: post #333
oblio wrote: post #298

Earlier quoted context omitted.

I didn't go that far, but for small movements I use arrow keys. hjkl don't make any sense to me and I'm not keen on using them just because someone had that keyboard layout in 1978.

They make sense because they are directly under your fingers, so you don't have to move them all the way over to the arrow keys and back just to move around. jkl; would make more sense, that's the only oddity.

There was a time that keyboard had their arrows keys on the left side. I forgot the source.

Re: Neovim 0.5 is overpowering

#362

Post by jrek »

pessimizer wrote: post #329
addicted wrote: post #325

Earlier quoted context omitted.

I think you’re overestimating how well real life actions map to the object/verb dichotomy. So you’d say that it’s object first because you first get the wood and saw and then decide to saw the wood with it. I could argue it’s verb first because you first GET the wood and saw. I’m not saying that I’m right and you’re wrong. In fact, quite the opposite. My point is that I don’t think real life actions can be broken cle…

"I need to GET something. I know, I'll GET some WOOD." "I need some WOOD. I think I'll GET some WOOD."

I think this supports the point - in either case the syntax for the action is 'get wood'.

Re: Neovim 0.5 is overpowering

#363

Post by alpaca128 »

nucleardog wrote: post #293
alpaca128 wrote: post #178

Earlier quoted context omitted.

You can often fix it with `:syntax sync fromstart`, but Vim's syntax highlighting just keeps being a bit weird.

I usually just keep space bound along the lines of: :noremap :silent noh echo :syn sync fromstart This recalculates syntax highlighting as well as removes highlighting on search results/etc. Basically, whenever stuff "looks weird", just mash space in normal mode and it fixes it. The fact that I have this bound to something like space should tell you how often I end up using it. :)

I recently gained a liking to search result highlighting, it's much more useful than I originally thought. The problem is not the highlighting itself but its persistence. I added a few autocmds to automatically hide it in certain events and a manual shortcut. Works better for me now, though it is annoying that `:noh` has some weird special status that makes it nonfunctional in autocmd.

Re: Neovim 0.5 is overpowering

#364

Post by oblio »

pfranz wrote: post #359
oblio wrote: post #298

Earlier quoted context omitted.

I didn't go that far, but for small movements I use arrow keys. hjkl don't make any sense to me and I'm not keen on using them just because someone had that keyboard layout in 1978.

How is that any weirder than WASD for FPS games? That was only codified a few decades ago on modern qwerty keyboards.

WASD is fine. Because WASD is organized like the arrow cluster and up is up, down is down (sort of, but the placement makes sense), left is left, right is right.

Re: Neovim 0.5 is overpowering

#365

Post by oblio »

the_duke wrote: post #333
oblio wrote: post #298

Earlier quoted context omitted.

I didn't go that far, but for small movements I use arrow keys. hjkl don't make any sense to me and I'm not keen on using them just because someone had that keyboard layout in 1978.

They make sense because they are directly under your fingers, so you don't have to move them all the way over to the arrow keys and back just to move around. jkl; would make more sense, that's the only oddity.

I don't like the line alignment.

They should be respecting their directions, like the arrow keys do. Think UHJK or IJKL. Plus they would need nubs or similar to make them stand out a bit.

At least for me.

Re: Neovim 0.5 is overpowering

#366

Post by devenvdev »

curriculum wrote: post #37

I'm most excited for the treesitter integration and its potential to amplify Vim's "killer feature": text editing as a language. Vim's editing language feels most powerful when I'm using its text objects: "ciw" means "change in word", "cis" means "change in sentence", and so on. But Vim's built-in text objects are not always a perfect match for the code you're editing. Suppose you want to change the first argument of…

Please someone clean that tpope searchlight! Na na na na na na na na tpope!

I would actually pay (although relatively small amount) for better programming text objects. It would feel so much more natural than the currently burned in muscle memory workarounds...

Re: Neovim 0.5 is overpowering

#367

Post by oblio »

coliveira wrote: post #156
oblio wrote: post #18

Earlier quoted context omitted.

The thing is, Vimscript sucks. Using a more mainstream language would be great for a modern advanced editor. Vim has a ton of Vimscript plugins but I wonder how long it will take the Neovim community to replicate most of their functionality in Lua. I'd guess that not that long.

There is a point when it doesn't make any difference if the language sucks or not. What matters is if it is capable. You can say the same about most successful languages: C sucks, shell script sucks, eLisp sucks, LaTeX sucks, but they're all there and will continue to be because they have been capable of support the communities for which they were designed. Now, you can freely dream about the perfect extension langua…

> Now, you can freely dream about the perfect extension language for UNIX, or vi, or TeX, or emacs, but it won't make any difference because nobody will move from something that works to an unproven extension language just because some people (usually the minority) feel that it is a more comfortable language for them.

Lua ia an extremely powerful and popular extension language. It probably has at least 10x the users that Vimscript has.

And people willingly choose Lua. Barely anyone chooses Vimscript, they're generally forced to use it.

If anything, Vimscript is the > extension language. It's in Vim because Bram made it the Vim language, but it was never voted on or designed. Vimscript will most likely die with Vim, because I'm quite convinced that outside of trolling attempts, no one will adopt it for another app ;-)

Re: Neovim 0.5 is overpowering

#368

Post by pdimitar »

otabdeveloper4 wrote: post #357
pdimitar wrote: post #48

NeoVIM seems like a big upgrade over a lot of editors. As a very casual Emacs user who never got excited enough for the "self-documenting and programmable editor" idea, VIM gets more appealing by the day for me. I am also using Spacemacs for a year or so and it's definitely better than normal Emacs. Haven't tried Doom Emacs and I doubt that I will, regardless of a lot of positive feedback. I mean, Emacs is alright bu…

> ...still prefer stuff to come semi-configured out of the box Maybe I'm weird, but stock GNU Emacs as out of the box is perfect for me. Tried configuring it with various bells-and-whistles over the years, but I always come back to stock Emacs. (And no, despite using Emacs for 25 years I don't write elisp.)

Well it absolutely isn't for me, f.ex. I constantly need project-wide functionality like find files by name or contents. Just using C-x C-f all the time is much more inefficient.

Re: Neovim 0.5 is overpowering

#369

Post by BadassFractal »

What's the recommended way to run nvim on macOS these days?

Just run it within Terminal? I recall that unlike on Ubuntu, there was some scrolling lag to it that might have required some tweaking. Not sure if that's the case anymore.

Re: Neovim 0.5 is overpowering

#370

Post by OJFord »

kbenson wrote: post #287
alpaca128 wrote: post #178

Earlier quoted context omitted.

You can often fix it with `:syntax sync fromstart`, but Vim's syntax highlighting just keeps being a bit weird.

I added 'autocmd BufEnter * syntax sync minlines=4000' to my .vimrc to make it buffer more of large files initially, so it gets less confused when you reopen a file and it resumes at a prior location deep inside and has no syntax highlighting. I guess fromstart would work as well, but is probably best manually run like you do so a very large file doesn't bring the system to a halt.

That's why that happens, and a fix - thanks!
Post reply on HN