On Fri, 2 Oct 2009 04:36:47 -0500, forgottenwizard wrote:

> > > It isn't always on the users sytem. Providing a non-existent default
> > > seems quite broken to me.
> > 
> > That's true of every editor, so you have to choose the one that is
> > most likely to be there, the one that is installed for the stage
> > tarballs and is there unless the user has taken specific steps to
> > remove it.
> 
> Or you could try to find a suitable default intelligently instead of
> blindly compiling in a default that may or may not exist. Worse still is
> blindly doing so without telling the user.

The user is told. the handbook clearly explains how and why to set
EDITOR. nano is only used when EDITOR cannot be found, in other words its
a suitable default for a broken system.

> And if you, say, have two editors installed that satisfy virtual/editor?

How is this a problem? As long as a working editor is available to edit
sudoers, nothing else is important, because once you are editing sudoers
you can change the default in there.

I fail to see why this is an issue in the first place, if you can set and
environment variable or add a single line to a config file, you really
should reconsider your choice of distro.

At least I've learned one thing from this thread, I didn't even know that
visduo had a built-in default choice of editor, mainly because it's
always used the one I wanted it to.


-- 
Neil Bothwick

Deja Foobar: A feeling of having made the same mistake before.

Attachment: signature.asc
Description: PGP signature

Reply via email to