When I run
sudo vipw or sudo vigr, it uses nano as the default editor. I've already
used update-alternatives to select vim as my default editor, but this
doesn't seem to work for vipw/vigr.
I have to do
sudo EDITOR=vim vipw
How can I make vim the default editor for vipw/vigr. Or how can I s
On Fri, Jan 05, 2018 at 03:00:43PM -0500, John Ratliff wrote:
> I have to do
>
> sudo EDITOR=vim vipw
>
> How can I make vim the default editor for vipw/vigr. Or how can I set the
> EDITOR variable when I use sudo automatically?
By default, sudo strips all the useful variables out of your enviro
On Fri, Jan 05, 2018 at 03:00:43PM -0500, John Ratliff wrote:
> When I run
>
> sudo vipw or sudo vigr, it uses nano as the default editor. I've already
> used update-alternatives to select vim as my default editor, but this
> doesn't seem to work for vipw/vigr.
>
> I have to do
>
> sudo EDITOR=v
On 05.01.2018 21:15, Greg Wooledge wrote:
> On Fri, Jan 05, 2018 at 03:00:43PM -0500, John Ratliff wrote:
>> sudo EDITOR=vim vipw
> Defaultsenv_reset
> Defaults:greg !env_reset
That basically keeps the *whole* environment, what is usually a security
issue. Better solution is to keep on
On Fri, Jan 05, 2018 at 09:37:16PM +0100, Ulf Volmer wrote:
> On 05.01.2018 21:15, Greg Wooledge wrote:
> > On Fri, Jan 05, 2018 at 03:00:43PM -0500, John Ratliff wrote:
>
> >> sudo EDITOR=vim vipw
>
> > Defaultsenv_reset
> > Defaults:greg !env_reset
>
> That basically keeps the *whole
On Fri, Jan 05, 2018 at 09:37:16PM +0100, Ulf Volmer wrote:
>
> That basically keeps the *whole* environment, what is usually a security
> issue. Better solution is to keep only needed and proved environment
> variables using
>
> Defaults env_keep += "EDITOR"
>
Allowing the EDITOR variable thro
On Fri 05 Jan 2018 at 21:37:16 +0100, Ulf Volmer wrote:
> On 05.01.2018 21:15, Greg Wooledge wrote:
> > On Fri, Jan 05, 2018 at 03:00:43PM -0500, John Ratliff wrote:
>
> >> sudo EDITOR=vim vipw
>
> > Defaultsenv_reset
> > Defaults:greg !env_reset
>
> That basically keeps the *whole* e
On 05.01.2018 21:46, Roberto C. Sánchez wrote:
> There is essentially no functional difference between allowing only the
> EDITOR variable and any arbitrary environment variable. Allowing EDITOR
> (or PAGER, or any other thing that sets the name of a command to
> execute) through to sudo provides
On 1/5/2018 3:25 PM, Roberto C. Sánchez wrote:
On Fri, Jan 05, 2018 at 03:00:43PM -0500, John Ratliff wrote:
When I run
sudo vipw or sudo vigr, it uses nano as the default editor. I've already
used update-alternatives to select vim as my default editor, but this
doesn't seem to work for vipw/vi
if you're in a hurry in this situation try:
apt-get remove --purge nano
problem solved?
--
CK
10 matches
Mail list logo