On Sun, Jul 19, 2015 at 07:23:44PM +0200, Nextime wrote:
> On July 19, 2015 7:07:09 PM CEST, Renaud OLGIATI <renaud@???> wrote:
> >On Sun, 19 Jul 2015 18:53:11 +0200
> >Didier Kryn <kryn@???> wrote:
> >

> >>      I agree with you that, if an editor is as small and more
> >intuitive 
> >> and self-explanatory than Nano, it can be a good choice. But let's
> >not 
> >> complicate the problem by envisionning too many combinations. The 
> >> proposed alternative was:
> >>      1) have nano and vi installed and nano as the default, like in
> >Debian
> >>      2) have vi only

> >
> >I fail to see the problem:
> >If I want to use vi, I invoque $ vi
> >if I want to use nano, I invoque $ nano
> >
> >The problem only arioe when I was sent to a rescus console, and $ vi
> >does not start anything, probably in hindsight because I have /usr on a
> >separate partition, and vi is unavailable in such a case.

*If* you have busybox installed, "busybox vi" should work.
Alternatively, install elvis-tiny.

> >And of course at the time I did not know about nano...
> >
> The issue, for me, is that after install i have to remove nano, or at
> least change the $EDITOR env var. I don't like to find nano when i do
> a crontab -e or a visudo.

update-alternatives --list editor
update-alternatives --set editor /usr/bin/vim.*

See update-alternatives(8) for more details.

> Anyway, the solution is already established, nothing will change in
> jessie, for ascii a menu will permit to choose the default editor,
> vim-tiny will be installed in any case.

I honestly hope that this "choose the default editor" menu does it right
and works with the alternatives system, rather than brute forcing the
issue by installing only one editor.

Thanks,
Isaac Dunham