171–180 of 429 posts
Watching ThePrimeagen and tjdevries has also given me some good insights into neovim. Tjdevries has put a lot of work nvim-treesiter, and it shows. I have stuck with regular vim for a while because I have everything configured the way I want, but I am setting up a new build now, and I will probably move to neovim.
btw I'm tj :]
Earlier quoted context omitted.
Do you find your brain can actually work that way? My issue with all of these relative jump points, repeat this N times, etc of VIM is by the time I’ve calculated in my mind what the command should be I’d have already done it with just standard navigation/mark/yank/repeat. But perhaps you have galaxy brain ;)
The way vim works is actually the opposite of what your brain wants, this is one of the reasons why learning vim tricks is hard. The vim model is "action-object" (eg dw, delete word). A more natural, friendly and interactive model is the opposite, "object-action": first you select the text, your editor highlights the text, then you apply actions to the selection, one by one, and see what happens after each one. Becau…
It always feels really nice knowing that people are getting excited by your work. Thanks for the shoutout! (I'm tjdevries) Happy to answer any nvim questions while I'm here.
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…
Do you find your brain can actually work that way? My issue with all of these relative jump points, repeat this N times, etc of VIM is by the time I’ve calculated in my mind what the command should be I’d have already done it with just standard navigation/mark/yank/repeat. But perhaps you have galaxy brain ;)
Earlier quoted context omitted.
All modern IDEs have vim bindings.
My experience is that many of them are shoddy experiences. Some might be really good though.
Neovim 0.5 is awesome. It has native LSP support, Lua configuration support that it feels like true revolution over past versions. But, getting into optimal setup in neovim/vim involves lot of configuration. Here is mine if you want to refer: https://github.com/varbhat/dotfiles/tree/main/dot_config/nvi...
Now, some off-topic musings:
I switched to Emacs from vi in the 80's, and I put up with it for the many powerful packages it has. Lisp as a configuration language has served Emacs well for decades, but I've always been aware that it narrows the number of contributors to those that are comfortable with Lisp. Progress towards modernizing the Emacs extension language has been slow...and it will still be a Lisp like language (Scheme).
I'm rooting for Neovim and I'd like to see a project like this for Emacs that would modernize it's UI, UX and underlying extension language. This will likely never happen while I'm still programming. Imagine the difficulty of recreating just the org-mode package!
Earlier quoted context omitted.
I'm excited about it because Vim's usual syntax highlighting is rather fragile. As far as I understand it Vim does the highlighting in the same thread, and to ensure good performance it enforces a time limit for the file parsing. In larger files this frequently leads to weirdly flickering highlighting when scrolling. Going from that to actual syntax parsing is a dream come true.
That explains a lot. I often have a syntax highlighting quirk where it thinks that a fold has an open quotation mark in it. And will highlight everything below the fold as if it's a part of a string. I unfold, and clears it all up. but it's annoying in the moment. I look forward to all of this
Earlier quoted context omitted.
Yeah, just recently I had to edit text like this 'name1', 'name2', 'name3', to: 'name1': Enum.Name1, 'name2': Enum.Name2, 'name3': Enum.Name3, by the time I figured out a sequence of keyboard commands I'm pretty sure I could have multicursored it pretty easily, go to name1, create 2 cursors, select word & copy, start typing : Enum., paste selected word, select word, capitalize, type , In vim it was something like qdy…
This looks like the sort of thing you would intuitively solve with visual selection and a regex. ``` Vjj:s/\v'(.*)',/'\1': Enum.\u\1,/ ``` This is all just muscle memory. It seems impossible until you get used to it, and then it's the most natural thing in the world.
It always feels really nice knowing that people are getting excited by your work. Thanks for the shoutout! (I'm tjdevries) Happy to answer any nvim questions while I'm here.