[haiku-development] Re: Vim episodes. IV. It is ready to breathe...

Fredrik Holmqvist <fredrik.holmqvist@xxxxxxxxx> wrote:
> 2009/5/7 Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>:
> > I would argue people who use the shell always need to know what
> > they
> > are doing.
> > If you are not only remotely connected to a system, you would use a
> > real editor, anyway.
> I disagree. Do we really want that kind of mentality, that you
> already
> have to know what you're doing before you start using the shell? Do
> we
> really want to use something that most users and some devs can't work
> with as a default editor?

Huh? The shell is simply not usable for someone that doesn't know how
to use it. Vim is mostly the same problem here, just a bit worse. I
can't recommend using vim for anyone that didn't read at least a short
guide yet. But the same goes for the shell, actually. That's not a
mentality, that's just how it is.
If you use vim even though you don't know how to use it, and have a GUI
editor installed (like StyledEdit), why not use that one instead?

> (Yes it's really powerful, but it's very unintuitive. Here is how I
> use it:
> Every time I get thrown into vi without me expecting it, like doing
> svn commit which uses the default editor I get really frustrated and
> annoyed. (In fact I want to throw the computer out the window). I
> usually use CTRL-Z and kill the process, because it's very
> unintuitive
> to even learn basic commands like help or quit.)

If you don't know vim, why do you start it in the first place? Just
because you heard it's an editor??
Why would you want to use commands you don't know to use? The shell
commands can be pretty destructive, and so you better always know what
you're doing.

Bye,
   Axel.

Other related posts: