Stephan Aßmus <superstippi@xxxxxx> wrote: > Jonas Sundström schrieb: > > "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> wrote: > >> I think one command line editor should really be > >> enough. Whether this is vim or nano I don't really > >> care about, but since we always had vim (even BeOS), > >> I would vote for that one. If you really need another > >> command line editor, just go ahead and install it. > > If a choice -has- to be made, I would say that the people > > who prefer vim are more likely to know how to install it. Hehe, almost good point :-) > > Minor issue - which editors to include - I know, but I > > find it interesting to question the CLI as a freehaven > > for (only) developers and experienced users / with a > > high tolerance for a steep learning curve. 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. [...] > If vi has to be present for POSIX compatibility, then so be it, but > please let that not force our choice of a sensible command line > editor > being available. "Oh, we don't like shipping two apps for the same > purpose? - Tough luck, vi(m) it has to be!" ;-) It's not like you get > one more choice when you right click a text file and go to "Open > With". > It's a complete non-brainer, something that doesn't ever get in the > way. > But the day I have to fix something remotely and find out I forgot to > install an alternative to vim would be a totally unnecessary > disappointment. If you have remote access, you can still just install nano with the great package manager we'll have then ;-) In any case, I got your point, but I still wouldn't really like to have two apps for the same purpose - for the sake of cleanliness. But I know how to use vim, so I am not sane anyway. How about a compromise: we don't include nano in the base install (that comes with no extra apps), but we do in the full distro? Someone could create an optional package for nano, too. Bye, Axel.