Bdale Garbee wrote:
On Sat, 2008-01-05 at 18:19 +0100, David Ayers wrote:
Please consider reverting to using /usr/bin/editor by default for
consistencies sake.
The problem, really, is choosing what to be consistent with. I was on
your side for a long time, then I was convinced to change so that a tool
with 'vi' in its name actually ran vi. [shrug]
OK, I guess this is indeed a question of perspective. Does one try to
be consistent with the name if the tool or consistent with the default
editor you configured for the system for all editor invocations.
I would argue that the bug is the name of the tool, which is why I could
conceive an 'editsudo' command that allows editing the sudoers file
without having to unexpectedly deal with vi while all other
administrative tasks could be done with the preferred editor.
In that case I could simply relearn to use a different command to edit
the sudoers file, which seems a lot less effort than to remember to set
an environment variable for every virtual host you need to setup just
before you edit and remember to set the default editor for subsequent
'sudo visudo' edits.
You raise an interesting point about sudoedit, though. It's a separate
source file from visudo. A patch so sudoedit uses /usr/bin/editor while
having visudo use /usr/bin/vi might make sense?
I think that could alleviate the issue a bit if one does not have edit
the sudoers file often on many machines. But it still seems awkward to
have to take extra configuration steps for this package to use a
'consistent' editor to administrate this one package while all other
packages would use the 'system default'.
I'm not sure how one could go about this and whether users should
somehow be surveyed. I'll stay open for discussion, yet will concede to
trying to remember to:
EDITOR=editor visudo
as root and remember to add
Default editor=/usr/bin/editor
for each system configuration since I don't want to evolve this into a
bike shed issue.
Cheers,
David
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
