[slim-vim] Vim like mappings for Emacs
Jim Bailey
dgym.bailey at gmail.com
Thu Nov 30 10:14:56 CST 2006
>
> No comments at all?
>
> Brad
>
Well you have gone from changing vim to make it more useful for
developing CL, to abandoning vim in favour of emacs. I'm not suprised
there aren't many comments.
Personally I think this last step is a shame. I think vim is
fundamentally flawed - at the code level, making it the better of many
evils, but still evil. I think emacs is also fundamentally flawed, not
just in terms of elisp, but also the whole mentality of defining a
billion key combos that I don't use, and stating that only 26 awkward
key combos are reserved for my usage.
I have used viper before and I don't like it, mostly because it goes
too far, assuming that if I want to use viper at all then I must want
to use viper all the time by default. Normally when I use emacs I just
get on and use it the "emacs" way and only want viper mode in those
instances where I want to do something I know how to do really easily
with vi, and can't imagine how to get the job done at all emacs. Maybe
this wouldn't be such a problem if viper wasn't so horribly backwards
and "vi", I only know my way round vim.
So what will vimper be? Something that breaks emacs, and
otherwise is just another vim implementation on a poor code base?
Hardly my ideal editor.
An editor written in Common Lisp would have been a huge step forward,
as a base for both single mode editing and vim style editing. I'm sorry
that that project floundered, I wish I had some time to help out with
it, but right now I am busy trying to sort out another big and still
unsolved problem : an actually portable GUI toolkit. This might take me
some time...
More information about the slim-vim
mailing list