2009/5/8 Fredrik Holmqvist <fredrik.holmqvist@xxxxxxxxx>: > 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? > > (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.) > > Fredrik Holmqvist, TQH > It was the same for me. Then I read the manual and now I can use it decently. The problem is that you are supposed to read some documentation to use something correctly. Always.