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.
Thank you for the nice work!
My pleasure :)
Neovim 0.5 is overpowering
191–200 of 429 posts
Re: Neovim 0.5 is overpowering
#192It's fast. Mind-blowingly fast. I used it since beta (heck, even alpha) on a 2014 Pentium laptop, and I built many, many engineering school projects on it.
VS Code used to take up the 1.8GB left from my measly 4GB.
Re: Neovim 0.5 is overpowering
#193Earlier quoted context omitted.
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…
You've oddly crystallized why Kakoune has so far failed to grab me! The description you gave of the actions one takes in editing makes sense: in most non-modal editors, you select the text you want to take actions on, then choose the action to take. But, I can do that in literally every modeless editor! That's the way essentially all of them work. But when people write of "Vim as a text editing language" as many comm…
> "[verb] the [noun]" is pretty natural
For an English speaker. There are many human languages that put the verb at the end of clauses. Japanese is one example.
Re: Neovim 0.5 is overpowering
#194Earlier quoted context omitted.
I don't agree that it requires a lot of configuration. Here is the "starter" configuration (~280 lines) that I made for helping debug user issues with the built-in language server client: https://github.com/mjlbach/defaults.nvim
You think 280loc as a starter is not much?
Sure, although this is fairly "batteries included". Very rough numbers:
- 34 lines to set up plugin manager/install plugins
- 43 for keybinds
- 35 for documentation
- 50 for autocompletion
- 20 for customizing one language server for plugin development (sumneko)
It adds up for sure, and neovim/vim/emacs are not ever likely going to be as plug & play as vscode/intellij, but I would argue the target user for vim/neovim/emacs is someone who wants more customization, which is almost always going to mean the configuration is more verbose.
If you have concrete suggestions on cutting down this config in particular, you can file an issue/PR. The main reason I created this, was because we (core neovim team) get a lot of "I just want something that works" type feedback (which to many includes autocompletion and default keybinds, which are almost 1/3 of the config)
Re: Neovim 0.5 is overpowering
#195Earlier 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…
> 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.
Do you mean that you think "word change" instead of "change word"? To me this sounds like you have been programming in Java-like languages for too long :)
Re: Neovim 0.5 is overpowering
#196Nowadays, I'm more tempted to use something more mouse focused for my geek itches. Like Acme, for example. Neovim looks cool, but I've long realized that I spend a lot more time reading than writing code. The automations and flexibility of the multi modal mode do not matter much for my use case.
Ironic, because vim and neovim are specifically designed for programmers that spend more time reading than writing code. You can get to damn near any line in a massive project with just a couple key strokes.
I understand that and I'm a heavy emacs user, but I feel that just browsing with the mouse and clicking symbols as if they were links to navigate leaves me with less cognitive overhead overall.
Re: Neovim 0.5 is overpowering
#197Earlier quoted context omitted.
You think 280loc as a starter is not much?
Sure, although this is fairly "batteries included". Very rough numbers: - 34 lines to set up plugin manager/install plugins - 43 for keybinds - 35 for documentation - 50 for autocompletion - 20 for customizing one language server for plugin development (sumneko) It adds up for sure, and neovim/vim/emacs are not ever likely going to be as plug & play as vscode/intellij, but I would argue the target user for vim/neovim…
VSC has tons of customizations available, perhaps even beating Vim in the number of exposed configurations. The problem with Vim configurations is that a lot of them feel obvious, and the ergonomics of dealing with configs is painful and frequently calls you to reference outside material.
Re: Neovim 0.5 is overpowering
#198I'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…
I just wish Vim had proper S-expression structural editing support. Many editors have vim support but very few have smartparens/paredit with good integration. If Vim can extend its language to include some basic structural editing, then writing any type of tag based code e.g. JSX would become much more pleasant. For example in VS Code's Flutter plugin there is support for "delete surrounding widget" and "wrap child widget in new widget". They just need better keybinding integration.
Re: Neovim 0.5 is overpowering
#199Earlier quoted context omitted.
Sure, although this is fairly "batteries included". Very rough numbers: - 34 lines to set up plugin manager/install plugins - 43 for keybinds - 35 for documentation - 50 for autocompletion - 20 for customizing one language server for plugin development (sumneko) It adds up for sure, and neovim/vim/emacs are not ever likely going to be as plug & play as vscode/intellij, but I would argue the target user for vim/neovim…
VSC has tons of customizations available, perhaps even beating Vim in the number of exposed configurations. The problem with Vim configurations is that a lot of them feel obvious, and the ergonomics of dealing with configs is painful and frequently calls you to reference outside material.
I'm not sure I'd say that it beats vim/neovim, but I agree with your point about ergonomics. I would say the vim manual is a fantastic resource, I've never felt the need to reference outside material.
Neovim has already integrated many of the "obvious defaults" (see :help nvim-defaults), but if you're a user and feel that something is missed you should file an issue.
I personally don't mind that the defaults may not be what I'd like, as once they are set, I spend very little time modifying my system configuration. I realize this can be a barrier to new users though.
Re: Neovim 0.5 is overpowering
#200I'm using vim happy no plugins no config just edit files do I need neovim?