On Freitag 02 Oktober 2009, Arthur D. wrote:
You appear to be demonstrating that you don't fully understand the
problem:
828 ~ $ grep nano /usr/portage/app-admin/sudo/sudo-1.7.2_p1.ebuild
# XXX: /bin/vi may not be available, make nano visudo's default.
Am 02.10.2009 07:29, schrieb Arthur D.:
I repeat once more.
Every user who has VIM installed on theirs systems is forced to do extra
configuration, to make sudo work as expected, just because someone prefer
other editor and thinks that vanilla choice is bad. Isn't that just stupid?
I have
On Fri, 2009-10-02 at 08:06 +0200, Volker Armin Hemmann wrote:
why is it always vim users who get their panties in a knot about
nothing?
You are likely wrong about this. I'm willing to bet that a lot of
people, even people responding to this thread, are vim users. However
most of us know how
I really don't see your problem.
All that was needed here on my box was setting VIM as my editor of
choice (I preferer to do that per-user so no setting of anything in rc
or /etc/env.d) and VISUDO accepted it. No magic involved.
Sebastian, I already fixed the problem for my local host. But I
2009/10/2 Arthur D. spinal...@mail.ru:
You appear to be demonstrating that you don't fully understand the
problem:
828 ~ $ grep nano /usr/portage/app-admin/sudo/sudo-1.7.2_p1.ebuild
# XXX: /bin/vi may not be available, make nano visudo's default.
--with-editor=/bin/nano
On Fri, Oct 2, 2009 at 2:30 AM, Joshua Murphy poiso...@gmail.com wrote:
2009/10/2 Arthur D. spinal...@mail.ru:
You appear to be demonstrating that you don't fully understand the
problem:
828 ~ $ grep nano /usr/portage/app-admin/sudo/sudo-1.7.2_p1.ebuild
# XXX: /bin/vi may not be
Go to LFS, build it all, build emacs, set EDITOR to emacs, and run
sudo visudo. Please. I have a rather good guess that you'll be,
amazingly, using the default that was set at build time for the sane
default editor, in LFS's case vim (whether called by that or the vi
symlink to it), that the
2009/10/2 Arthur D. spinal...@mail.ru:
Go to LFS, build it all, build emacs, set EDITOR to emacs, and run
sudo visudo. Please. I have a rather good guess that you'll be,
amazingly, using the default that was set at build time for the sane
default editor, in LFS's case vim (whether called by
if I
run a server with 50 users, 48 of which use emacs, one of which uses
vim, and I choose to use pico, why should I be forced to use vi for it
by default just because I have vim to satisfy someone else's desires?
That's really funny, Joshua. Do you provide 50 users of your company with
access
Joshua Murphy poiso...@gmail.com писал(а) в своём письме Fri, 02 Oct
2009 09:58:33 +0300:
every Gentoo system has vi, there just isn't a direct
symlink with that name to busybox.
Wow, that's a really great problem.
$ ln `which busybox` vi
$ ./vi
--
Best regards, Spinal
On Fri, 02 Oct 2009 08:29:30 +0300, Arthur D. wrote:
I repeat once more.
Every user who has VIM installed on theirs systems is forced to do extra
configuration, to make sudo work as expected, just because someone
prefer other editor and thinks that vanilla choice is bad. Isn't that
just
On Thu, 1 Oct 2009 19:34:25 -0500, forgottenwizard wrote:
So instead it should set a non-existant editor to the configured
default?
Nano is not non-existent by default.
Another variable in make.conf may be a reasonable fix for this though
I'm sure someone will bitch about having to set
On Fri, 02 Oct 2009 09:44:26 +0300, Arthur D. wrote:
That's right. But there are some reasons why visudo called so (do you
see that short VI?),
What are those reasons?
Do they apply to Gentoo?
Is it possible that this is simply because the original coder used vi? Or
perhaps to maintain the
On Fri, 02 Oct 2009 10:17:26 +0300, Arthur D. wrote:
I remind you, that an admin restricted the access to that ticket after
users started to vote for it.
Unless the reason for restriction was stated, your implication of
causality is invalid.
--
Neil Bothwick
Plagarism prohibited. Derive
A more sensible approach would be for the ebuild to check which ebuild
satisfies the virtual/editor dependency and set that.
Not clever. What if there are several editors installed?
And, yes, I prefer VIM. And I don't like when the package which
vanilla defaults were always to be using vim as
On Fri, 02 Oct 2009 11:15:09 +0300, Arthur D. wrote:
A more sensible approach would be for the ebuild to check which ebuild
satisfies the virtual/editor dependency and set that.
Not clever. What if there are several editors installed?
Choose the most appropriate from a defined list.
Neil Bothwick n...@digimed.co.uk писал(а) в своём письме Fri, 02 Oct
2009 11:23:38 +0300:
This problem could also be fixed by USE flags. Instead of whining why
not submit a patch that has the ebuild respect the vanilla USE flag?
Thanks for the idea. I will try this.
--
Best regards, Spinal
On Fri, Oct 02, 2009 at 09:07:20AM +0100, Neil Bothwick wrote:
On Thu, 1 Oct 2009 19:34:25 -0500, forgottenwizard wrote:
So instead it should set a non-existant editor to the configured
default?
Nano is not non-existent by default.
It isn't always on the users sytem. Providing a
Am 02.10.2009 08:25, schrieb Arthur D.:
I really don't see your problem.
All that was needed here on my box was setting VIM as my editor of
choice (I preferer to do that per-user so no setting of anything in rc
or /etc/env.d) and VISUDO accepted it. No magic involved.
Sebastian, I already
Once again, try running sudo visudo as unprivileged user (that's
right,
sudo is used to make root stuff without logging with root ;-) )
Ok, I comment out
%wheel ALL=(ALL) ALL
so that my user could use sudo visudo.
Hey.. Great.. It started visudo with VIM.
So again.. What are you complaining
On Fri, Oct 02, 2009 at 09:23:38AM +0100, Neil Bothwick wrote:
On Fri, 02 Oct 2009 11:15:09 +0300, Arthur D. wrote:
And, yes, I prefer VIM. And I don't like when the package which
vanilla defaults were always to be using vim as editor is overwritten
without any notifications and causing
Am 02.10.2009 10:52, schrieb forgottenwizard:
On Fri, Oct 02, 2009 at 09:07:20AM +0100, Neil Bothwick wrote:
On Thu, 1 Oct 2009 19:34:25 -0500, forgottenwizard wrote:
So instead it should set a non-existant editor to the configured
default?
Nano is not non-existent by default.
It isn't
Arthur D. wrote:
Once again, try running sudo visudo as unprivileged user (that's
right,
sudo is used to make root stuff without logging with root ;-) )
Ok, I comment out
%wheel ALL=(ALL) ALL
so that my user could use sudo visudo.
Hey.. Great.. It started visudo with VIM.
So again..
On Fri, Oct 02, 2009 at 11:08:08AM +0200, Sebastian Be?ler wrote:
Am 02.10.2009 10:52, schrieb forgottenwizard:
It isn't always on the users sytem. Providing a non-existent default
seems quite broken to me.
By DEFAULT it is on EVERY Gentoo-system.
If you CHOOSE to remove the default then
Am 02.10.2009 11:04, schrieb forgottenwizard:
The number of USE flags would be quite impressive for such a small
package.
a vanilla-flag could be possible that disables every changes to the
upstream-package.
It even exists atm for a number of packages
metat...@darkstation ~ $ euse -i vanilla
On Fri, 2 Oct 2009 04:04:30 -0500, forgottenwizard wrote:
This problem could also be fixed by USE flags. Instead of whining
why not submit a patch that has the ebuild respect the vanilla USE
flag?
USE flags is nice, except ls /usr/portage/app-editors/ | wc -l returns
76 packages (give
On Fri, 2 Oct 2009 03:52:24 -0500, forgottenwizard wrote:
Nano is not non-existent by default.
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
On Fri, Oct 02, 2009 at 11:21:08AM +0200, Sebastian Be?ler wrote:
Am 02.10.2009 11:04, schrieb forgottenwizard:
The number of USE flags would be quite impressive for such a small
package.
a vanilla-flag could be possible that disables every changes to the
upstream-package.
It even
On Fri, Oct 02, 2009 at 10:29:08AM +0100, Neil Bothwick wrote:
On Fri, 2 Oct 2009 03:52:24 -0500, forgottenwizard wrote:
Nano is not non-existent by default.
It isn't always on the users sytem. Providing a non-existent default
seems quite broken to me.
That's true of every editor,
Am 02.10.2009 11:29, schrieb forgottenwizard:
insert emacs user whining
Thats an option, but seems to be a poor one. All that will do is let you
use either vi(m) or nano for the default, which for emacs users will be
no diffrent than the current problem.
joke
If you use emacs then you are
Am 02.10.2009 11:40, schrieb Sebastian Beßler:
Am 02.10.2009 11:29, schrieb forgottenwizard:
insert emacs user whining
Thats an option, but seems to be a poor one. All that will do is let you
use either vi(m) or nano for the default, which for emacs users will be
no diffrent than the
On Freitag 02 Oktober 2009, forgottenwizard wrote:
On Fri, Oct 02, 2009 at 10:29:08AM +0100, Neil Bothwick wrote:
On Fri, 2 Oct 2009 03:52:24 -0500, forgottenwizard wrote:
Nano is not non-existent by default.
It isn't always on the users sytem. Providing a non-existent default
OK. Now the latest update.
1) Here's a copy (just a copy, all links are useless) of bug report done
by me.
I was forced to copy that page to hosting because package maintainer
restricted
access to users who began to vote for this bug.
On Fri, Oct 02, 2009 at 11:40:33AM +0200, Sebastian Be?ler wrote:
Am 02.10.2009 11:29, schrieb forgottenwizard:
insert emacs user whining
Thats an option, but seems to be a poor one. All that will do is let you
use either vi(m) or nano for the default, which for emacs users will be
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
This thread is really out of control, I doubt anything useful can be born
here, we are just running circles around a chair.
On Fri, 2 Oct 2009 04:54:42 -0500, forgottenwizard
phrexianrea...@hushmail.com wrote:
On Fri, Oct 02, 2009 at 11:40:33AM +0200, Sebastian Be?ler wrote:
Am 02.10.2009
On Fri, 02 Oct 2009 12:09:23 +0200, Jesús Guerrero wrote:
The USE flag idea is non-viable and doesn't make sense.
Why not? The flag already exists for the very purpose the OP raised.
--
Neil Bothwick
PC DOS Error #01: Windows loading, come back tomorrow
signature.asc
Description: PGP
On Thu, 01 Oct 2009 23:12:36 +0300, Arthur D. spinal...@mail.ru wrote:
James Ausmus james.aus...@gmail.com писал(а) в своём письме Thu, 01
Oct
2009 22:04:38 +0300:
VI.
Maybe it's called VIsudo because VIM is better alternative for VANILLA,
hah?
Maybe we should stick to the old devfs
Volker Armin Hemmann wrote:
then the more sensible one should be used by default.
Lets see:
nano, built in help, easy to use, small, good enough for most edits.
vim, whatthefuckisthatcrap? how do I quit this monstrum? what happened now?
MODES?
nano wins, hands down. Because every idiot
Oh, and your ebuild patch doesn't even bother to check the vim
dependency.
The vanilla USE flag is not global, it's local, man.
And it doesn't force user to install vim.
You may want to make symlink /usr/bin/vi - /bin/busybox instead.
--
Best regards, Spinal
On Fri, 2 Oct 2009 11:21:53 +0100, Neil Bothwick n...@digimed.co.uk
wrote:
On Fri, 02 Oct 2009 12:09:23 +0200, Jesús Guerrero wrote:
The USE flag idea is non-viable and doesn't make sense.
Why not? The flag already exists for the very purpose the OP raised.
Oh, you meant vanilla, sorry, I
On Fri, 02 Oct 2009 13:35:47 +0300, Arthur D. spinal...@mail.ru wrote:
Oh, and your ebuild patch doesn't even bother to check the vim
dependency.
The vanilla USE flag is not global, it's local, man.
That's irrelevant. Each ebuild should sort its dependencies. The scope of
the use flags is
So, if it can't find vim, we should go
fix that ourselves and that is acceptable, but if it can't find nano then
that's unacceptable for you, did I get it right?
Did you visit
http://www.rootshell.be/~spinal/gentoo_bug_report/286017.html ?
I was forced to offer the maintainer to respect at
On Fri, 02 Oct 2009 13:57:44 +0300, Arthur D. spinal...@mail.ru wrote:
So, if it can't find vim, we should go
fix that ourselves and that is acceptable, but if it can't find nano
then
that's unacceptable for you, did I get it right?
Did you visit
On Fri, Oct 02, 2009 at 12:09:23PM +0200, Jes??s Guerrero wrote:
On Fri, 2 Oct 2009 04:54:42 -0500, forgottenwizard
phrexianrea...@hushmail.com wrote:
How about a custom_editor flag, as you suggested, then an EDITOR
variable in make.conf? Thats the only way I could see being able to
solve
On 10/2/2009 1:29 AM, Arthur D. wrote:
Agree. There's no need in making vim as depends. But in other hand in
vanilla sudo
package there's VI hardcoded by default. And MOST if not ALL users who
have VIM
So basically, you're entire silly argument boils down to I
don't like nano, make it go
On Friday 02 October 2009 10:53:37 Arthur D. wrote:
=+ 3) And now the most interesting. I was banned by maintainer. Now I cannot
access the ticket too.
Strange, uh?
2009/10/2 Mike Edenfield kut...@kutulu.org:
On 10/2/2009 1:29 AM, Arthur D. wrote:
Agree. There's no need in making vim as depends. But in other hand in
vanilla sudo
package there's VI hardcoded by default. And MOST if not ALL users who
have VIM
So basically, you're entire silly argument
This is an interesting thread to analyze, even though 90.9% of it is
basically BS and flaming.
I actually can side a little bit with the OP. But as a user of Gentoo,
vi and sudo.
If it were all up to me, I'd have visudo look at EDITOR and fail if it
doesn't exist. But this is likely not the
2009/10/2 Arthur D. spinal...@mail.ru:
Joshua Murphy poiso...@gmail.com писал(а) в своём письме Fri, 02 Oct 2009
09:58:33 +0300:
every Gentoo system has vi, there just isn't a direct
symlink with that name to busybox.
Wow, that's a really great problem.
$ ln `which busybox` vi
$ ./vi
--
Hello, happy Gentoo users! I'm new on this distro, so I'm sorry if you
consider to be stupid what I gonna say.
Many of us prefer editors other than nano. Some of us believe in ideas of
freedom and choice which Gentoo provides us with. But...
There're ones who prefer primitive hardcoding over
On 10/1/2009 10:44 AM, Arthur D. wrote:
I just installed VIM with emerge, and removed nano because I considered
it to be absolutely unnecessary in my system. Why I need nano? I am a VIM
fan. And here the troubles begin...
Run sudo visudo and you get this:
~ $ sudo visudo
visudo: no editor found
On Donnerstag 01 Oktober 2009, Arthur D. wrote:
Hello, happy Gentoo users! I'm new on this distro, so I'm sorry if you
consider to be stupid what I gonna say.
Many of us prefer editors other than nano. Some of us believe in ideas of
freedom and choice which Gentoo provides us with. But...
Arthur D. wrote:
Hello, happy Gentoo users! I'm new on this distro, so I'm sorry if you
consider to be stupid what I gonna say.
Many of us prefer editors other than nano. Some of us believe in ideas of
freedom and choice which Gentoo provides us with. But...
There're ones who prefer
On Thu, 2009-10-01 at 17:44 +0300, Arthur D. wrote:
[long post about something relatively trivial]
sudoedit (and others) use the EDITOR (or VISUAL or whatever) environment
variable to chose an editor.
Gentoo defaults to nano. It's easy to change it (most experienced Linux
users do).
# emerge
Arthur D. wrote:
Many of us prefer editors other than nano.
Me included. I don't have nano installed here - I use LE.
The package SUDO. It is one of the most mandatory packages in distro.
Hmm. It's not even installed on any of my 15 systems - no use for it
whatsoever.
The default editor is
On Thu, Oct 1, 2009 at 11:11 AM, Albert Hopkins mar...@letterboxes.org wrote:
[very clear, consice, polite answer to the OP's question]
And he's right, as a meta distribution, it just works is generally
*not* regarded as a Gentoo principle to shoot for.
And oddly, in fact, it usually it's
Thanks for your replies, guys.
2. Change the default editor on your system by putting something in
/etc/env.d:
apollo ~ # cat /etc/env.d/99editor
EDITOR=vim
--Mike
===
spi...@supervisor ~ $ cat /etc/env.d/99editor
# Configuration file for
On Thu, 01 Oct 2009 17:44:41 +0300, Arthur D. wrote:
My quests leaded me to the ebuild
of sudo. And I saw this nice shiny line there:
--with-editor=/bin/nano
P.S. Having defaults is not bad. But they should not override our
favourites.
What you you think that line in the ebuild does? It
On 1 Oct 2009, at 15:44, Arthur D. wrote:
...
I just installed VIM with emerge, and removed nano because I
considered
it to be absolutely unnecessary in my system. Why I need nano? I am
a VIM
fan. And here the troubles begin...
Run sudo visudo and you get this:
~ $ sudo visudo
visudo:
On 1 Oct 2009, at 16:40, Stroller wrote:
...
So it seems to me that you're right. It appears like maybe when
`sudo` detects that it's running `visudo` it does seem to ignore
$EDITOR. I, too, disagree with this behaviour. IMO the ebuild (--
with-editor=/bin/nano) take the editor from
Arthur D. wrote:
The first option works fine, but ... how much time should the user
spend to get things just work as expected?
Plainly put, Gentoo isn't an easy-to-use distro. If it were, I don't
think I would be using it, paradoxically enough. If spending a little
time learning about and
On Thu, 01 Oct 2009 18:58:43 +0300, Arthur D. wrote:
1. emerge -C nano
2. emerge vim
3. export EDITOR=`which vim`
4. Or do eselect editor - env-update ; or edit /etc/rc.conf -
env-update 5. Reemerge sudo if you wish (it will not change anything)
6. Relogin
7. Run sudo visudo
You get this:
1. emerge -C nano
2. emerge vim
3. export EDITOR=`which vim`
4. Or do eselect editor - env-update ; or edit /etc/rc.conf -
env-update 5. Reemerge sudo if you wish (it will not change anything)
6. Relogin
7. Run sudo visudo
You get this:
visudo: no editor found (editor path = /bin/nano)
No I
2009/10/1 Arthur D. spinal...@mail.ru:
Hello, happy Gentoo users! I'm new on this distro, so I'm sorry if you
consider to be stupid what I gonna say.
Many of us prefer editors other than nano. Some of us believe in ideas of
freedom and choice which Gentoo provides us with. But...
There're
On Thu, 01 Oct 2009 19:21:07 +0300, Arthur D. wrote:
I gonna bet you added magic line to your sudoers previously or make
some other
crutches to make it work:
Defaults env_keep=EDITOR
You lost that bet.
--
Neil Bothwick
Is it possible to be totally partial?
signature.asc
Description:
I gonna bet you added magic line to your sudoers previously or make
some other
crutches to make it work:
Defaults env_keep=EDITOR
You lost that bet.
Proof?
Section 8.c of the Gentoo Handbook (called System Information) advises
you to edit /etc/rc.conf to change your preferences.
Daniel, I
2009/10/1 Arthur D. spinal...@mail.ru:
I gonna bet you added magic line to your sudoers previously or make
some other
crutches to make it work:
Defaults env_keep=EDITOR
You lost that bet.
Proof?
Section 8.c of the Gentoo Handbook (called System Information) advises
you to edit
I'm using a 4 years old system, and if I change that line, log out and
in again, it changes the env variable and everything works (that means
the behavior is probably caused by your configuration). If visudo is
still using that configuration, maybe that's because some
configuration file has
As the access to the bug was denied by the admin please use this link for
discussion:
http://forums.gentoo.org/viewtopic-t-795069.html
Thanks.
--
Best regards, Spinal
2009/10/1 Arthur D. spinal...@mail.ru
I'm using a 4 years old system, and if I change that line, log out and
in again, it changes the env variable and everything works (that means
the behavior is probably caused by your configuration). If visudo is
still using that configuration, maybe
James Ausmus, I solved this proble long ago. I just curios,
why it's not solved by portage? So the users should spend their
time diggin in manuals to find why is sudo not working in Gentoo
like it does in LFS or any other distro?.. Is this the Gentoo way
or something?
--
Best regards, Spinal
On Donnerstag 01 Oktober 2009, Arthur D. wrote:
As the access to the bug was denied by the admin please use this link for
discussion:
http://forums.gentoo.org/viewtopic-t-795069.html
Thanks.
wow, you must have been VERY obnoxious to have the bug closed for others.
First time I see that.
On 1 Oct 2009, at 19:07, Volker Armin Hemmann wrote:
On Donnerstag 01 Oktober 2009, Arthur D. wrote:
As the access to the bug was denied by the admin please use this
link for
discussion:
http://forums.gentoo.org/viewtopic-t-795069.html
wow, you must have been VERY obnoxious to have the
On 1 Oct 2009, at 19:40, Stroller wrote:
On 1 Oct 2009, at 19:07, Volker Armin Hemmann wrote:
On Donnerstag 01 Oktober 2009, Arthur D. wrote:
As the access to the bug was denied by the admin please use this
link for
discussion:
http://forums.gentoo.org/viewtopic-t-795069.html
wow, you
On Thu, 01 Oct 2009 21:10:19 +0300, Arthur D. wrote:
James Ausmus, I solved this proble long ago. I just curios,
So you're just ranting, you don't actually have a problem to solve and
your question was rhetorical venting?
why it's not solved by portage?
What problem? That the default editor
On Thu, 01 Oct 2009 20:34:15 +0300, Arthur D. wrote:
Man, running sudo visudo and just running visudo is not the same.
True, but both call $EDITOR here.
Be careful. Nano is hardcoded in sudo's ebuild.
Yes, as a default when no other editor is specified. That means no
$EDITOR variable visible
2009/10/1 Arthur D. spinal...@mail.ru
James Ausmus, I solved this proble long ago. I just curios,
why it's not solved by portage? So the users should spend their
time diggin in manuals to find why is sudo not working in Gentoo
like it does in LFS or any other distro?.. Is this the Gentoo way
On Thu, Oct 01, 2009 at 05:08:16PM +0100, Stroller wrote:
On 1 Oct 2009, at 16:40, Stroller wrote:
...
So it seems to me that you're right. It appears like maybe when
`sudo` detects that it's running `visudo` it does seem to ignore
$EDITOR. I, too, disagree with this behaviour. IMO
Arthur D. wrote:
James Ausmus, I solved this proble long ago. I just curios,
why it's not solved by portage? So the users should spend their
time diggin in manuals to find why is sudo not working in Gentoo
like it does in LFS or any other distro?.. Is this the Gentoo way
or something?
Am Donnerstag 01 Oktober 2009 21:32:56 schrieb forgottenwizard:
However, I'm also wondering why the ebuild doesn't make use of the
EDITOR variable as was mentioned.
Because that's the worst thing to do. An ebuild's behaviour should not depend
on env variables (like it's still the case for
Perhaps you should find a distribution more suited to your
abilities/expectations. Clearly,
Gentoo is not for you.
Really? Do you just give up and eat what people tell you to eat?
I don't respect such people, really.
I prefer to change the things, that I think are not right.
Obtruding the
Dirk Heinrichs dirk.heinri...@online.de писал(а) в своём письме Thu, 01
Oct 2009 22:45:40 +0300:
Am Donnerstag 01 Oktober 2009 21:32:56 schrieb forgottenwizard:
However, I'm also wondering why the ebuild doesn't make use of the
EDITOR variable as was mentioned.
Because that's the worst
James Ausmus james.aus...@gmail.com писал(а) в своём письме Thu, 01 Oct
2009 22:04:38 +0300:
The Gentoo Way of doing things is to stick as close to vanilla
upstream as possible, and to enable you to have complete control over
your box, including configurations. In other words, if you want
On 10/1/2009 1:34 PM, Arthur D. wrote:
I'm using a 4 years old system, and if I change that line, log out and
in again, it changes the env variable and everything works (that means
the behavior is probably caused by your configuration). If visudo is
still using that configuration, maybe that's
On 10/1/2009 3:32 PM, forgottenwizard wrote:
However, I'm also wondering why the ebuild doesn't make use of the
EDITOR variable as was mentioned. This defaults to nano so it should
work fine in a default install, and would avoid issues like this which
seems to be an arguement that the dev(s)
I would be hesitant to use a user-specific variable like EDITOR to
define the system-wide default on an ebuild. For example, what if my
EDITOR was set to gvim or emacs when I installed sudo, then some other
remote user tried to run visudo over ssh?
Consider that gvim will be just a
On 1 Oct 2009, at 21:28, Mike Edenfield wrote:
On 10/1/2009 3:32 PM, forgottenwizard wrote:
However, I'm also wondering why the ebuild doesn't make use of the
EDITOR variable as was mentioned. This defaults to nano so it should
work fine in a default install, and would avoid issues like this
On Donnerstag 01 Oktober 2009, Stroller wrote:
On 1 Oct 2009, at 21:28, Mike Edenfield wrote:
On 10/1/2009 3:32 PM, forgottenwizard wrote:
However, I'm also wondering why the ebuild doesn't make use of the
EDITOR variable as was mentioned. This defaults to nano so it should
work fine in a
On 1 Oct 2009, at 22:01, Volker Armin Hemmann wrote:
On Donnerstag 01 Oktober 2009, Stroller wrote:
On 1 Oct 2009, at 21:28, Mike Edenfield wrote:
On 10/1/2009 3:32 PM, forgottenwizard wrote:
However, I'm also wondering why the ebuild doesn't make use of the
EDITOR variable as was
On Thu, 01 Oct 2009 23:45:51 +0300, Arthur D. wrote:
It's like, oh, please you install nano, or I refuse to run.
It's nothing like that at all. As long as you have an editor installed
and configured correctly, visudo will quite happily run without nano.
--
Neil Bothwick
Help put the fun
On Thu, 01 Oct 2009 23:12:36 +0300, Arthur D. wrote:
I think it's most reasonably to omit that hardcoding line from ebuild.
I think you need to re-read the ebuild. sudo depends on virtual/editor,
not nano. Nowhere is nano hardcoded to be a requirement of sudo. On the
other hand, if you went
On 1 Oct 2009, at 23:53, Neil Bothwick wrote:
On Thu, 01 Oct 2009 23:12:36 +0300, Arthur D. wrote:
I think it's most reasonably to omit that hardcoding line from
ebuild.
I think you need to re-read the ebuild. sudo depends on virtual/
editor,
not nano. Nowhere is nano hardcoded to be a
On Fri, 2 Oct 2009 00:54:50 +0100, Stroller wrote:
I think you need to re-read the ebuild. sudo depends on virtual/
editor,
not nano. Nowhere is nano hardcoded to be a requirement of sudo. On
the
other hand, if you went with the upstream settings, you'd need to
add vim
as a
On Thu, Oct 01, 2009 at 09:45:40PM +0200, Dirk Heinrichs wrote:
Am Donnerstag 01 Oktober 2009 21:32:56 schrieb forgottenwizard:
However, I'm also wondering why the ebuild doesn't make use of the
EDITOR variable as was mentioned.
Because that's the worst thing to do. An ebuild's behaviour
On Thu, Oct 01, 2009 at 12:04:38PM -0700, James Ausmus wrote:
2009/10/1 Arthur D. spinal...@mail.ru
The Gentoo Way of doing things is to stick as close to vanilla upstream as
possible, and to enable you to have complete control over your box,
including configurations. In other words, if you
In response to the subject and the OP . . .
YES!
If you'd rather have your free OS accommodate your needs, then perhaps
you should find/create one. Otherwise, shut up or make your
suggestions less obnoxious (realizing the non-native English issue).
The OP's position (from what I can tell) has
On Thu, 2009-10-01 at 20:55 -0500, Neal Hogan wrote:
To claim that I try to change things that are 'wrong' (I fight for
injustice) is silly, in this context. This is not civil rights . . .
this is not genocide . . . this is an OS distro that is free and MAY
fit your needs. To complain about
You appear to be demonstrating that you don't fully understand the
problem:
828 ~ $ grep nano /usr/portage/app-admin/sudo/sudo-1.7.2_p1.ebuild
# XXX: /bin/vi may not be available, make nano visudo's default.
--with-editor=/bin/nano \
How so? That config option for sudo
99 matches
Mail list logo
