> Well, I prefer Perl over Python.  I know a lot more Perl than Python,
> and generally prefer Perl over Python.  You make some good points
> about other applications, though, I must admit.
I don't know either language well enough for it to concern me overly much.

> > We should aim to provide all the features that the Emacs Slime does,
> > but with more Vim-like key access.
>
> :)  Interesting that you should put it that way.  Part of me wants to
> say, "If that's all you want, we should just work on making Viper mode
> in (X)Emacs closer to Vim."  That part of me has been at war (well,
> "in conflict") with the part that wants to re-implement slime.el in
> Perl.

I know the feeling! :)  I personally find it hard to properly use
Viper mode in Emacs, this may be because Viper mode more closely
emulates vi.  Though I got the feeling that Viper is a kind of no mans
land, unloved by either Emacs or Vim fans.

> The more Lisp I learn and do, the more attractive Emacs gets, as a
> concept.
Yes, but I prefer the Vim "there is one way to do it, here is the key
mappings" approach to the Emacs "there are many ways to do it,
download any of these .el files, or alternately extend the editor
yourself!"
It feels to me as if the Emacs philosophy would still be there if we
simply improved Viper - and I am sure that most people use Vim or
Emacs for the philosophy as much  as the key mappings

> * Pros/cons of refining Viper to look more like Vim:
>
>   - Pro: don't have to port slime.el to some other language; lots of
>     effort saved
  Though you still need to create Vim-like Slime mappings...

My gut tells me that we ought to write a Perl or Python frontend for
Swank because it will open Swank up for use outside of Emacs - many
other tools can be made to work with Perl or Python.  Perl will
probably be prefered because it is Larry's preference.

Being very handwavy here, I think that Emacs or Vim is the editor of
choice for maybe 80-90% of Unix programmers.  And among the C-like
languages, the Vim/Emacs split is probably about 50/50.  At the moment
the Vim using Lisp converts (lets say ~40% of Unix programmers) have
an extra barrier to learning Lisp - Emacs.  Many Vimmers
can't/won't/don't want to use Emacs, so I think there is significant
motivation for extending Vim to nicely support Lisp - which right now
means supporting a Slime-like environment.

Cheers
Brah
_______________________________________________
Gardeners mailing list
[email protected]
http://www.lispniks.com/mailman/listinfo/gardeners

Reply via email to