if you're in a hurry in this situation try:
apt-get remove --purge nano
problem solved?
--
CK
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 wor
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 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 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, 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 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 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.
>
>
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 var
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
Almost forgot: in mc's "Options" drop-down menu, uncheck "Use
internal editor."
(My taste is to use mc's internal viewer, so I leave that box
checked.)
--
IMPORTANT: This email is intended for the use of the individual
addressee(s) named above and may contain information that is
confidential,
Put in your ~/.bashrc lines like this:
export EDITOR="vim.tiny"
export VISUAL=$EDITOR
Exit the current login session and then log in again, or load
the new contents of ~/.bashrc with
$ . ~/.bashrc
Convince yourself that all is well in the environment with:
$ env
--
IMPORTANT: This email is
On 10/07/2016 06:11 PM, David Wright wrote:
On Fri 07 Oct 2016 at 17:46:15 (-0400), Tony Baldwin wrote:
On 10/07/2016 05:38 PM, Adrian Bunk wrote:
On Fri, Oct 07, 2016 at 05:23:00PM -0400, Tony Baldwin wrote:
Why is mc using nano when vim.tiny is set as my editor upon
update-alternatives --c
On 10/07/2016 05:58 PM, Adrian Bunk wrote:
On Fri, Oct 07, 2016 at 05:46:15PM -0400, Tony Baldwin wrote:
On 10/07/2016 05:38 PM, Adrian Bunk wrote:
On Fri, Oct 07, 2016 at 05:23:00PM -0400, Tony Baldwin wrote:
Why is mc using nano when vim.tiny is set as my editor upon
update-alternatives --
On 10/07/2016 05:57 PM, Charlie wrote:
On Fri, 7 Oct 2016 17:46:15 -0400 Tony Baldwin sent:
Apparently nothing, but when I do update-alternatives to set it, It
shows that vim.tiny is currently the chosen default (visudo uses it)
How do I set $EDITOR if not with update-alternatives?
On 10/07/2016 05:58 PM, Adrian Bunk wrote:
export EDITOR=vim.tin
I've learned recently whil using this to configure $PATH, Tat this is
going to set it for the current session only.
How can I make it permanent?
thanks,
Tony
--
http://tonybaldwin.me
all tony, all the time
On Fri 07 Oct 2016 at 17:46:15 (-0400), Tony Baldwin wrote:
> On 10/07/2016 05:38 PM, Adrian Bunk wrote:
> >On Fri, Oct 07, 2016 at 05:23:00PM -0400, Tony Baldwin wrote:
> >>Why is mc using nano when vim.tiny is set as my editor upon
> >>update-alternatives --config editor?, and, of course, mc is s
On Fri, Oct 07, 2016 at 05:46:15PM -0400, Tony Baldwin wrote:
> On 10/07/2016 05:38 PM, Adrian Bunk wrote:
> > On Fri, Oct 07, 2016 at 05:23:00PM -0400, Tony Baldwin wrote:
> > > Why is mc using nano when vim.tiny is set as my editor upon
> > > update-alternatives --config editor?, and, of course,
On Fri, 7 Oct 2016 17:46:15 -0400 Tony Baldwin sent:
> Apparently nothing, but when I do update-alternatives to set it, It
> shows that vim.tiny is currently the chosen default (visudo uses it)
> How do I set $EDITOR if not with update-alternatives?
After contemplation, my reply is:
I u
On 10/07/2016 05:38 PM, Adrian Bunk wrote:
On Fri, Oct 07, 2016 at 05:23:00PM -0400, Tony Baldwin wrote:
Why is mc using nano when vim.tiny is set as my editor upon
update-alternatives --config editor?, and, of course, mc is set to NOT use
mcedit, its internal editor
What does "echo $EDITOR" sa
On Fri, Oct 07, 2016 at 05:23:00PM -0400, Tony Baldwin wrote:
> Why is mc using nano when vim.tiny is set as my editor upon
> update-alternatives --config editor?, and, of course, mc is set to NOT use
> mcedit, its internal editor
What does "echo $EDITOR" say in your shell?
The update-alternative
Why is mc using nano when vim.tiny is set as my editor upon
update-alternatives --config editor?, and, of course, mc is set to NOT
use mcedit, its internal editor
tony
--
http://tonybaldwin.me
all tony, all the time
On Wed, Mar 19, 2003 at 03:39:58PM -0800, Craig Dickson wrote:
> Alan Shutko wrote:
>
> > Will Yardley <[EMAIL PROTECTED]> writes:
> >
> > > Alan Shutko <[EMAIL PROTECTED]>:
> > >
> > >> Some programs use VISUAL, some EDITOR, some both... the distinction
> > >> between them has long been lost.
>
On Wed, Mar 19, 2003 at 07:41:07PM -0500, Alan Shutko wrote:
> Craig Dickson <[EMAIL PROTECTED]> writes:
>
> > And by way of illustrating just how worthless the distinction is these
> > days... when was the last time you actually used a line editor
> > interactively?
>
> It's been a couple years,
Craig Dickson <[EMAIL PROTECTED]> writes:
> And by way of illustrating just how worthless the distinction is these
> days... when was the last time you actually used a line editor
> interactively?
It's been a couple years, but I've been known to use it to fix a
broken system... 8^)
--
Alan Shut
On Thu, 20 Mar 2003 00:20:39 +0100 "Marco d'Itri" <[EMAIL PROTECTED]> wrote:
> On Mar 19, Will Yardley <[EMAIL PROTECTED]> wrote:
> >Yes, but mutt (normally) obeys VISUAL if present - it's only the
> >Debian package which seems not to.
> Maybe you think this because the debian package is a 1.5 sn
provide reference to authoritative documentation about
> the correct semantics of $EDITOR and $VISUAL (I could not find any)
> and a patch implementing this.
The first relevant document I found was the tcsh manual page[1], which
states that:
EDITOR The pathname to a default edito
Alan Shutko wrote:
> Will Yardley <[EMAIL PROTECTED]> writes:
>> The patch (to init.c) seems to be:
>>
>>Tempdir = safe_strdup ((p = getenv ("TMPDIR")) ? p : "/tmp");
>> - Editor = safe_strdup ((p = getenv ("EDITOR")) ? p : "vi");
>> + Editor = safe_strdup ((p = getenv ("EDITOR")) ? p : "/u
Alan Shutko wrote:
> Will Yardley <[EMAIL PROTECTED]> writes:
>
> > Alan Shutko <[EMAIL PROTECTED]>:
> >
> >> Some programs use VISUAL, some EDITOR, some both... the distinction
> >> between them has long been lost.
> >
> > Perhaps, but EDITOR is supposed to be your line editor, and VISUAL your
>
On Mar 19, Will Yardley <[EMAIL PROTECTED]> wrote:
[FYI: since somebody asked about it, bidirectional gating will be
enabled for all linux.debian.* newsgroups hopefully before the end of
the month, as soon as I can change what is needed in the software.
News->mail gating for linux.debian.user will
Will Yardley <[EMAIL PROTECTED]> writes:
> The patch (to init.c) seems to be:
>
>Tempdir = safe_strdup ((p = getenv ("TMPDIR")) ? p : "/tmp");
> - Editor = safe_strdup ((p = getenv ("EDITOR")) ? p : "vi");
> + Editor = safe_strdup ((p = getenv ("EDITOR")) ? p : "/usr/bin/editor");
>Visua
[ Bcc to md at linux.it; package maintainer
see
http://lists.debian.org/debian-user/2003/debian-user-200303/msg03514.html]
In linux.debian.user, you wrote:
> [EMAIL PROTECTED] (Will Yardley) writes:
>> Shouldn't VISUAL (if present) override /usr/bin/editor as the
>> default full-screen editor?
On Wed, 19 Mar 2003 21:04:25 + (UTC), Faheem Mitha
<[EMAIL PROTECTED]> wrote:
> On Tue, 18 Mar 2003 21:15:28 -0800, Will Yardley <[EMAIL PROTECTED]> wrote:
>> [ Tried to post to linux.debian.user, but apparently this doesn't work
>> at the moment, unfortunately. ]
>
> Try the public access ne
On Tue, 18 Mar 2003 21:15:28 -0800, Will Yardley <[EMAIL PROTECTED]> wrote:
> [ Tried to post to linux.debian.user, but apparently this doesn't work
> at the moment, unfortunately. ]
Try the public access newsserver gmane.org. For more information see
the web page of the same name. The group corre
[EMAIL PROTECTED] (Will Yardley) writes:
> Shouldn't VISUAL (if present) override /usr/bin/editor as the
> default full-screen editor?
Some programs use VISUAL, some EDITOR, some both... the distinction
between them has long been lost. Set them both and it'll work almost
everywhere.
--
Alan Sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Mar 18, 2003 at 09:15:28PM -0800, Will Yardley wrote:
> [ Tried to post to linux.debian.user, but apparently this doesn't work
> at the moment, unfortunately. ]
linux.debian.user (and for that matter, any of the other newsgroups
this mailing l
[ Tried to post to linux.debian.user, but apparently this doesn't work
at the moment, unfortunately. ]
I noticed that when I have /usr/bin/editor set to nano on a system, but
I have:
export VISUAL=vim
in my environment, mutt still seems to use nano as the editor; however
if I put:
export EDITOR=vi
Brian Nelson <[EMAIL PROTECTED]> writes:
> John Griffiths <[EMAIL PROTECTED]> writes:
>
> > Hi all
> >
> > tryng to change the default editor on a potato 2.2.r4 system so users
> > who're not comfortable with vi can use mutt to send messages
>
John Griffiths <[EMAIL PROTECTED]> writes:
> Hi all
>
> tryng to change the default editor on a potato 2.2.r4 system so users
> who're not comfortable with vi can use mutt to send messages
>
> I tried:
>
> EDITOR=jed; export EDITOR
>
> which works unt
Hi all
tryng to change the default editor on a potato 2.2.r4 system so users
who're not comfortable with vi can use mutt to send messages
I tried:
EDITOR=jed; export EDITOR
which works until the user logs out
any thoughts on making it stick?
regs,
John
M> For some reason after installing and reinstalling vim, ae still remains
M> the default editor.
M> when I look in /etc/alternatives I see:
M> lrwxrwxrwx1 root root7 Apr 30 23:12 editor ->
M> /bin/ae
M> lrwxrwxrwx1 root root 21 Apr 30 2
Mark wrote:
>
> For some reason after installing and reinstalling vim, ae still remains
> the default editor.
>
> when I look in /etc/alternatives I see:
> lrwxrwxrwx1 root root7 Apr 30 23:12 editor ->
> Is there some debian specific setup script th
On Mon, 30 Apr 2001 14:26:46 Mark wrote:
> For some reason after installing and reinstalling vim, ae still remains
> the default editor.
update-alternatives --config editor
Debian provides a whole bunch of very nifty update-* scripts.
Some of them are (man -k update-):
update-alternati
Mark <[EMAIL PROTECTED]> wrote:
>For some reason after installing and reinstalling vim, ae still remains
>the default editor.
>
>when I look in /etc/alternatives I see:
>lrwxrwxrwx1 root root7 Apr 30 23:12 editor ->
>/bin/ae
>lrwxrwxrwx1 root
For some reason after installing and reinstalling vim, ae still remains
the default editor.
when I look in /etc/alternatives I see:
lrwxrwxrwx1 root root7 Apr 30 23:12 editor ->
/bin/ae
lrwxrwxrwx1 root root 21 Apr 30 23:12 editor.1.gz ->
/usr/man/man
VI. Also,
I believe that ae is the default editor, although there was a heated
debate on debian-devel a while back about the default editor. Our
beloved VIM lost out because people said it wasn't intuitive and
that it was too hard to learn . You can take my VIM when you
pry it from my cold, de
It's been a while since I've last installed Debian from scratch. Is ViM
the default vi clone installed? I thought it was another clone. Anyone
know?
Rob
===
[EMAI
47 matches
Mail list logo
