Live data from Hacker News

Modeless Vim

github.com

331–340 of 398 posts

Re: Modeless Vim

#331

Earlier quoted context omitted.

Seriously, it hurts. It makes sense, but it hurts. If only there were a more gentle path to editor modes. Maybe some simple graphical representation of the modes and commands that could be down in the corner? Like a dynamic vim infographic that clued a user into the most likely commands.

Helix is beginner friendly. It's keybindings make more sense than vim's.

Helix is wonderful. I did make one keybinding change: Switching in and out of Insert mode is CTRL-i so I don't have to wander off to the escape key so often.

Re: Modeless Vim

#332

My usual comment on any thread touching vim, as an answer to all hypothetical comments talking about how vim never clicked : Remap the Escape key to CapsLock else you will never like vim (provided you are a normal person) It's the most important key and you should punctuate all your inserts with it. So it'd better not be the key that's the furthest away from your fingers. The reason that's the case is an historical a…

The caps lock key is definitely using prime real estate on a keyboard for something that doesn't get used often.

I have taken to remapping it to a function key, moving caps lock to function+shift. Function+tab is mapped to escape, a combination I can easily press with my pinky alone.

This allows me to map a lot of the keys that would require moving my hand to function+[alphanumeric key], function+i is insert, function+u is page up, function+j is page down, function+r is home, function+f is end, and other such combinations.

I use a keyboard that supports QMK, so all of this customization is on the keyboard, but this could probably be done with software running on the computer, like AutoHotKey on Windows.

Re: Modeless Vim

#334

Earlier quoted context omitted.

If I remap CapsLock to Escape, then how will I enable cruise control for awesome mode? But seriously, I have hitting escape muscle memory engrained, I cannot remap it to any key because I won't ever think to hit capslock even if it's ergonomically "better"

I thought that, remapped it, and it turned out to be incredibly easy to swap over. I think it's because it's so much nicer to use.

My point is that it's NOT nicer to use for me.

I just instinctively did it to see my motion and it's an awkward feeling for me to move my left pinky over to the capslock key, definitely something I have to be mindful of doing to make happen and probably will take a long time for me to get used to.

Meanwhile, I actually extend my ring finger up and barely touch the escape and move it back down, all of that is very comfortable for me and I can do it without looking 100% of the time and never miss it.

Re: Modeless Vim

#335

My usual comment on any thread touching vim, as an answer to all hypothetical comments talking about how vim never clicked : Remap the Escape key to CapsLock else you will never like vim (provided you are a normal person) It's the most important key and you should punctuate all your inserts with it. So it'd better not be the key that's the furthest away from your fingers. The reason that's the case is an historical a…

The caps lock key is definitely using prime real estate on a keyboard for something that doesn't get used often. I have taken to remapping it to a function key, moving caps lock to function+shift. Function+tab is mapped to escape, a combination I can easily press with my pinky alone. This allows me to map a lot of the keys that would require moving my hand to function+[alphanumeric key], function+i is insert, functio…

On a Mac you can do this rebinding entirely natively within the system keyboard settings.

Re: Modeless Vim

#336
post #130

Earlier quoted context omitted.

Yeah but it’s a small island. If you learn Vim you’ll have access to Vi and Vi-like interfaces in lots of other software including terminals, database clients and everything that uses readline.

Curious what kind of interfaces you're thinking about? (Aside from vi, vim, nvim) From my experience anything with "vi navigation" basically just means using the home row keys for navigation + modes. So I haven't come across many interfaces yet where the verb order differences between helix/vim come into play.

i3 window manager leans heavily on vim defaults for navigating windows.

Re: Modeless Vim

#337
post #302

Earlier quoted context omitted.

Where do you map it that way?

As my sibling commenter said, use Karabiner Elements if you are on macos. Though it's not an out-of-the-box thing. Add this config to ~/.config/karabiner/assets/complex_modifications/custom-capslock.json { "title": "Change caps_lock to Esc and Control", "rules": [ { "description": "Post Esc if Caps is tapped, Control if held.", "manipulators": [ { "type": "basic", "from": { "key_code": "left_control", "modifiers": {…

Ooh! Can I do this with "z" and "/" (letter if tapped, control if held)?

Re: Modeless Vim

#338
post #37

Conceptually 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

Maybe putting diesel generator in a Tesla so you can use it even though charging is not your cup of tea.

Re: Modeless Vim

#339
post #37

Conceptually 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.

I disagree. It makes no more sense than turning a modeless editor into a modal one. Just use the right tool for the job.

Re: Modeless Vim

#340
post #37

Conceptually 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.

Seriously, it hurts. It makes sense, but it hurts. If only there were a more gentle path to editor modes. Maybe some simple graphical representation of the modes and commands that could be down in the corner? Like a dynamic vim infographic that clued a user into the most likely commands.

If I had a lot more free time, I've been noodling with some designs for a text editor with modes. It would start up by default in the equivalent of vim's insert mode where all the normal CUA keybindings (e.g. ctrl-c for copy) worked. But with many more. Then, if you go to the equivalent of normal mode you can just press X to do the same thing ctrl-X does in insert mode.
Post reply on HN