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
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
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
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
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
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
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.
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
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
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
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
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
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
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
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
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
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
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
22 matches
Mail list logo
