1 |
> |
2 |
> Talking specifically about sudo, I think you're making a big deal out of |
3 |
> a very minor thing, primarily because I cannot think of a sane example |
4 |
> of when $EDITOR and $VISUAL are not set and visudo (which requires an |
5 |
> interactive editor) would be invoked. |
6 |
|
7 |
|
8 |
It's problem exist for any package use configure for set default editor. |
9 |
If i'm not use nano (see sudo ebuild) and not set EDITOR i'm got bug. |
10 |
|
11 |
|
12 |
> I dont have much of an opinion on these things, although I think |
13 |
> expecting /bin/vi to be an screen oriented interactive editor (not |
14 |
> nescessarily vi) should be a sane assumption, and if it isnt, that is |
15 |
> the real bug. |
16 |
|
17 |
|
18 |
Okey. Then remove DEPEND virtual/editor from sudo and other package with |
19 |
hardcoded default editor. |
20 |
Set instead right editor. For example nano or vi. Or set USE flag for |
21 |
switch. |
22 |
|
23 |
I really hate nano and pico, I cannot understand how people use them, it |
24 |
> isnt the default because I'm a closet pico fan, I can assure you :) |
25 |
|
26 |
|
27 |
Gentoo contains same editors provided virtual/editor. We got two ways. |
28 |
Create virtual-editor package & wrapper or remove provide virtual-editor. |
29 |
|
30 |
sudo's default fallback is /bin/vi, but I received some bugs about this |
31 |
> several years ago, and after some discussion on -dev, we decided that |
32 |
> nano should take this place. Things have changed since then, nano used |
33 |
> to be `special` in that we could make assumptions about it, maybe i'll |
34 |
> change it back to /bin/vi, but I dont think it matters much. |
35 |
|
36 |
|
37 |
Set any editor but set right depend not virtual/editor. |