nanosudo?

[NoOp]

On 12/23/2012 01:48 PM, Phil Dobbin wrote:
> Hi, all.
> 
> I've just spun up a 12.04 remote virtual machine & when I ran the visudo
> command, it plonked me into nano. Whilst this is easy to fix (sudo
> update-alternatives --config editor), I'm puzzled as to when this happened.
> 
> I know it happened on some of the Red Hat clones but it was duly
> reported upstream as a bug & upstream confirmed it was bug.
> 
> Is it a bug on Ubuntu or is this behaviour now the default?

My 12.04 defaults to vi(m) per
<http://manpages.ubuntu.com/manpages/precise/man8/visudo.8.html>
" There is a hard-coded list of one or more editors that visudo will use
       set at compile-time that may be overridden via the editor sudoers
       Default variable.  This list defaults to "/usr/local/bin/vi"."

However it is not a new 12.04 install, but instead upgraded over time
from Dapper on up. I guess it changed to nano around 8.10 according to this:

<https://help.ubuntu.com/community/Sudoers>
"For Ubuntu 8.10: The default editor for visudo has changed to
sensible-editor. sensible-editor defaults to nano now, and select-editor
(which will run by default the first time) allows you to select another
one. "