[dead]
Modeless Vim
101–110 of 398 posts
Re: Modeless Vim
#102Seems maybe author did not know that this is already built into vim?: "easy vim", aka evim, or "vim -y". see "man vim" That said, if modeless editor you are looking for... then vim is not the editor you're looking for. It goes against what vim is, and hamstrings it. Learning vim is a journey, and once comfort sets in, you will understand why, why vim.
Good to know. Of course, I did have to google how to quit easy vim.
> I did have to google how to quit easy vim.
For those who know how to quit vim, but want to experience "how do I quit" again, try running `:term`.
Re: Modeless Vim
#103Conceptually the reasons the author give for this (syntax highlighting and other features of vim outclass other terminal-based editors) make total sense. That said there's something absolutely defiling about this. It's like installing a V8 in a Tesla, or replacing the pumpkin in pumpkin pie. I love that it will make VIM more accessible for more people, but I hate how they do it. Kudos to the author.
For those who don't know, there are at least two different V8-powered Teslas.
Re: Modeless Vim
#104I've always disliked that Bram calls Vim a "modal" editor. All this means is your keyboard and mouse actions do different things based on what "mode" of the editor you're in. All editors are "modal" editors. In VSCode for example, if you've focused the search box, pressing up loads the previous search, compared to if you've focused the code area, pressing up goes up a line. Vim purports to be more efficient than othe…
That's not really the same thing though is it? Each of vim's modes are extremely complex with their own usage of the vim grammar. The "modal" behavior you describe is very simple.
Re: Modeless Vim
#105Conceptually the reasons the author give for this (syntax highlighting and other features of vim outclass other terminal-based editors) make total sense. That said there's something absolutely defiling about this. It's like installing a V8 in a Tesla, or replacing the pumpkin in pumpkin pie. I love that it will make VIM more accessible for more people, but I hate how they do it. Kudos to the author.
> It's like installing a V8 in a Tesla, or replacing the pumpkin in pumpkin pie. Most pumpkin pies are actually made with butternut squash and other similar squashes, not pumpkin. https://en.wikipedia.org/wiki/Cucurbita_moschata https://www.thekitchn.com/whats-actually-in-your-canned-pump...
In most countries outside the US, squash is called pumpkin.
Re: Modeless Vim
#106Conceptually the reasons the author give for this (syntax highlighting and other features of vim outclass other terminal-based editors) make total sense. That said there's something absolutely defiling about this. It's like installing a V8 in a Tesla, or replacing the pumpkin in pumpkin pie. I love that it will make VIM more accessible for more people, but I hate how they do it. Kudos to the author.
> It's like installing a V8 in a Tesla, or replacing the pumpkin in pumpkin pie. Most pumpkin pies are actually made with butternut squash and other similar squashes, not pumpkin. https://en.wikipedia.org/wiki/Cucurbita_moschata https://www.thekitchn.com/whats-actually-in-your-canned-pump...
I've heard this claim various times, but it doesn't really make a lot of sense. Butternut squash has a carb:fiber ratio of about 6:1. Canned pumpkin is more like 3.5:1. Sure, the USDA might be lax on the precise definition of the word "pumpkin", but I don't expect them to go so easy on the nutrition data.
As Wikipedia notes:
>The term [pumpkin] is most commonly applied to round, orange-colored squash varieties, though it does not possess a scientific definition and may be used in reference to many different squashes of varied appearance.
If the article is simply intending to say that it does not usually come from squashes that are orange, oblate and ridged, then that's fair. But I don't think it's mostly butternut squash, and I don't see why manufacturers would try to hide using the most popular variety of squash.
Re: Modeless Vim
#107Earlier quoted context omitted.
I wonder which sort of features they could have in mind, if learning the basic modes is too hard for the intended user of the plugin.
They mention that as well - syntax highlighting is one example.
nano of course has syntax highlighting, so I’m curious where it falls short.
Re: Modeless Vim
#108Earlier quoted context omitted.
> Back in my day, when we pressed Ctrl+S, the terminal froze, and that's just the way we liked it. I don't think anyone needs (or even wants) the terminal to freeze on such a common shortcut in 2024. Personally, I have reclaimed Ctrl S for word delete (usually done by Alt-d)
Related: why does the shortcut to delete back a word (^W), close my browser tab?
Delete current word, delete current tab. Its related.
Re: Modeless Vim
#109Is this so you can look cool and say you "use vim btw" while not getting any of the benefits of using vim?