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
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
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
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
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
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"
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
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
12 matches
Mail list logo
