| 1 |
Хм. Да уж... ( |
| 2 |
Первое, что я делаю в свежеустановленной системе это правлю в rc.conf: |
| 3 |
|
| 4 |
#EDITOR="/bin/nano" |
| 5 |
EDITOR="/usr/bin/vim" |
| 6 |
#EDITOR="/usr/bin/emacs" |
| 7 |
|
| 8 |
Затем: |
| 9 |
emerge vim |
| 10 |
emerge -C nano |
| 11 |
|
| 12 |
2009/10/1 Arthur D. <spinal.by@××××.ru> |
| 13 |
|
| 14 |
> Понятно. Сейчас сделаем тред на офф форуме. Всем кому не безразлично -- |
| 15 |
>> просьба поддержать тему. |
| 16 |
>> |
| 17 |
>> Можно ли продублировать текст бага? Если можно -- скиньте сюда. |
| 18 |
>> |
| 19 |
> |
| 20 |
> Bug#: 286017 |
| 21 |
> app-admin/sudo-1.7.2_p1: default editor set in ebuild forces user to have |
| 22 |
> nano installed. |
| 23 |
> |
| 24 |
> I'm vim user, so I removed nano editor which was installed in stage3. |
| 25 |
> When I run command: |
| 26 |
> ------------------------------------------------- |
| 27 |
> ~ $ sudo visudo |
| 28 |
> visudo: no editor found (editor path = /bin/nano) |
| 29 |
> ~ $ env | grep -i edit |
| 30 |
> EDITOR=/usr/bin/vim |
| 31 |
> ------------------------------------------------- |
| 32 |
> I think the editor should not be hardcoded in ebuild. |
| 33 |
> Or it should be changed back to vim (which is sudo's default) because vim |
| 34 |
> is |
| 35 |
> better than nano. |
| 36 |
> Or there's a better solution: add USE flag to ebuild, so user could choose |
| 37 |
> the |
| 38 |
> editor to be compiled in. |
| 39 |
> |
| 40 |
> Reproducible: Always |
| 41 |
> |
| 42 |
> Steps to Reproduce: |
| 43 |
> 1. emerge -C nano |
| 44 |
> 2. emerge vim |
| 45 |
> 2. Run "sudo visudo" as an unprivileged user |
| 46 |
> |
| 47 |
> Actual Results: |
| 48 |
> Error message: |
| 49 |
> visudo: no editor found (editor path = /bin/nano) |
| 50 |
> |
| 51 |
> Expected Results: |
| 52 |
> visudo should be run with my favourite editor, which is VIM. |
| 53 |
> |
| 54 |
> |
| 55 |
> -- |
| 56 |
> Best regards, Spinal |
| 57 |
> |
| 58 |
> |
Archives