Vi is a poor implementation of a great idea. I would really like a modal editor in which I could configure the behavior for each key, maybe even define more modes and composable functions.
:help map.txtHistory of Emacs and vi Keys (2010)
71–80 of 91 posts
Re: History of Emacs and vi Keys (2010)
#72Vi is a poor implementation of a great idea. I would really like a modal editor in which I could configure the behavior for each key, maybe even define more modes and composable functions.
I've seen some work like this with 4coder. Having extensions written with native code that is dynamically linked makes this sort of thing make more sense if you want to minimize lag.
4coder is still very alpha at this point is easy to break but the low level primitives exposed leave it open for easy experimentation with little cruft to peal away first. It also very C++ focused so YMMV.
Re: History of Emacs and vi Keys (2010)
#73Vi is a poor implementation of a great idea. I would really like a modal editor in which I could configure the behavior for each key, maybe even define more modes and composable functions.
:help map.txt
Yes, I am well aware that I could remap everything. It's still not as malleable as I would like.
Re: History of Emacs and vi Keys (2010)
#74Re: History of Emacs and vi Keys (2010)
#75Earlier quoted context omitted.
Yes, I am well aware that I could remap everything. It's still not as malleable as I would like.
What exactly is missing? The tinymode, the tinykeymap (and others) plugins emulate some sort of temporary modes.
Rather than map over already-defined keys, it would be nice to have a clean slate to work from.
Re: History of Emacs and vi Keys (2010)
#76Earlier quoted context omitted.
What exactly is missing? The tinymode, the tinykeymap (and others) plugins emulate some sort of temporary modes.
Rather than map over already-defined keys, it would be nice to have a clean slate to work from.
So, "I want cake! Ok, here is cake. No! I want it to be feed to me also."
Sometimes, you should accept the 80% (or 97% in this case) solution and not pine for 100%. Or, scratch your own itch instead of whining no one else is offering to.
Re: History of Emacs and vi Keys (2010)
#77I never understood appeal of wasd. Maybe my fingers are shorter. It's way easier for me to have all three on same line so I change S to fwd and X to back.
Re: History of Emacs and vi Keys (2010)
#78Earlier quoted context omitted.
Rather than map over already-defined keys, it would be nice to have a clean slate to work from.
So, "I want cake! Ok, here is cake. No! I want it to be feed to me also." Sometimes, you should accept the 80% (or 97% in this case) solution and not pine for 100%. Or, scratch your own itch instead of whining no one else is offering to.
> Or, scratch your own itch instead of whining no one else [who] is offering to.
I'm working on it, but these things take time.
I don't see how it hurts to express my thoughts here. I wasn't asking anyone to do anything, just expressing something that I want, in case it already exists, or there are others who share my desire for it.
Re: History of Emacs and vi Keys (2010)
#79Earlier quoted context omitted.
What exactly is missing? The tinymode, the tinykeymap (and others) plugins emulate some sort of temporary modes.
Rather than map over already-defined keys, it would be nice to have a clean slate to work from.
So, you want an editor that doesn't do anything when you press a key? I'm not sure if such an app would have many users. :-)
Re: History of Emacs and vi Keys (2010)
#80Vi is a poor implementation of a great idea. I would really like a modal editor in which I could configure the behavior for each key, maybe even define more modes and composable functions.
Emacs? It has a gajillion modes.