| 1 |
On 10/01/2009 11:58 AM, Arthur D. wrote: |
| 2 |
> Neil Bothwick <neil@××××××××××.uk> ïèñàë(à) â ñâî¸ì ïèñüìå Thu, 01 Oct |
| 3 |
> 2009 18:45:20 +0300: |
| 4 |
> |
| 5 |
>>> My quests leaded me to the ebuild |
| 6 |
>>> of sudo. And I saw this nice shiny line there: |
| 7 |
>>> --with-editor=/bin/nano |
| 8 |
>> |
| 9 |
>>> P.S. Having defaults is not bad. But they should not override our |
| 10 |
>>> favourites. |
| 11 |
>> |
| 12 |
>> What you you think that line in the ebuild does? It changes the *default* |
| 13 |
>> editor for visudo. If you want something else, all you need to do is set |
| 14 |
>> your system up accordingly as described in the installation instructions |
| 15 |
>> of the handbook. |
| 16 |
>> |
| 17 |
>> PS Good luck getting anything changed to suit your demands with your |
| 18 |
>> attitude. You don't pay the devs enough for them to put up with that. |
| 19 |
> |
| 20 |
> OK. One more time. |
| 21 |
> 1. emerge -C nano |
| 22 |
> 2. emerge vim |
| 23 |
> 3. export EDITOR=`which vim` |
| 24 |
> 4. Or do eselect editor -> env-update ; or edit /etc/rc.conf -> env-update |
| 25 |
> 5. Reemerge sudo if you wish (it will not change anything) |
| 26 |
> 6. Relogin |
| 27 |
> 7. Run "sudo visudo" |
| 28 |
> You get this: |
| 29 |
> visudo: no editor found (editor path = /bin/nano) |
| 30 |
> |
| 31 |
|
| 32 |
Step 5a: echo 'Defaults editor=/usr/bin/vim' >> /etc/sudoers |
Archives