less calls nano instead of vi
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
In the default configuration of Ubuntu 18 LTS server, pressing the V key in less
calls the nano
editor instead of vi
while none of the environment variables $LESSEDIT
, $VISUAL
or $EDITOR
are set.
I was able to restore the correct behavior as documented in man less
with update-alternatives --set editor /usr/bin/vim.basic
but this proves less
executes editor
instead of vi
.
Is this a documentation bug (Ubuntu behavior intentionally differing from default upstream less
behavior) or a bug in less or is it my fault (did I miss something) ?
command-line vim less
add a comment |Â
up vote
3
down vote
favorite
In the default configuration of Ubuntu 18 LTS server, pressing the V key in less
calls the nano
editor instead of vi
while none of the environment variables $LESSEDIT
, $VISUAL
or $EDITOR
are set.
I was able to restore the correct behavior as documented in man less
with update-alternatives --set editor /usr/bin/vim.basic
but this proves less
executes editor
instead of vi
.
Is this a documentation bug (Ubuntu behavior intentionally differing from default upstream less
behavior) or a bug in less or is it my fault (did I miss something) ?
command-line vim less
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
In the default configuration of Ubuntu 18 LTS server, pressing the V key in less
calls the nano
editor instead of vi
while none of the environment variables $LESSEDIT
, $VISUAL
or $EDITOR
are set.
I was able to restore the correct behavior as documented in man less
with update-alternatives --set editor /usr/bin/vim.basic
but this proves less
executes editor
instead of vi
.
Is this a documentation bug (Ubuntu behavior intentionally differing from default upstream less
behavior) or a bug in less or is it my fault (did I miss something) ?
command-line vim less
In the default configuration of Ubuntu 18 LTS server, pressing the V key in less
calls the nano
editor instead of vi
while none of the environment variables $LESSEDIT
, $VISUAL
or $EDITOR
are set.
I was able to restore the correct behavior as documented in man less
with update-alternatives --set editor /usr/bin/vim.basic
but this proves less
executes editor
instead of vi
.
Is this a documentation bug (Ubuntu behavior intentionally differing from default upstream less
behavior) or a bug in less or is it my fault (did I miss something) ?
command-line vim less
edited Aug 17 at 15:04
muru
129k19271462
129k19271462
asked Aug 17 at 12:47
Juergen
273
273
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
6
down vote
accepted
It's a documentation bug in the man page, the behavior is documented in /usr/share/doc/less/README.Debian
).
In Debian and its derivatives (like Ubuntu) programs must use editor
as standard editor if neither $VISUIAL
nor $EDITOR
is set, see the Debian policy manual.
Do you think I should create a Debian documentation bug for this or will that be ignored anyway in favor of more important bugs ?
– Juergen
Aug 17 at 13:44
Theless
package already contains a patch for the manpage so the maintainer seems to care about this kind of things.
– Florian Diesch
Aug 18 at 8:40
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
accepted
It's a documentation bug in the man page, the behavior is documented in /usr/share/doc/less/README.Debian
).
In Debian and its derivatives (like Ubuntu) programs must use editor
as standard editor if neither $VISUIAL
nor $EDITOR
is set, see the Debian policy manual.
Do you think I should create a Debian documentation bug for this or will that be ignored anyway in favor of more important bugs ?
– Juergen
Aug 17 at 13:44
Theless
package already contains a patch for the manpage so the maintainer seems to care about this kind of things.
– Florian Diesch
Aug 18 at 8:40
add a comment |Â
up vote
6
down vote
accepted
It's a documentation bug in the man page, the behavior is documented in /usr/share/doc/less/README.Debian
).
In Debian and its derivatives (like Ubuntu) programs must use editor
as standard editor if neither $VISUIAL
nor $EDITOR
is set, see the Debian policy manual.
Do you think I should create a Debian documentation bug for this or will that be ignored anyway in favor of more important bugs ?
– Juergen
Aug 17 at 13:44
Theless
package already contains a patch for the manpage so the maintainer seems to care about this kind of things.
– Florian Diesch
Aug 18 at 8:40
add a comment |Â
up vote
6
down vote
accepted
up vote
6
down vote
accepted
It's a documentation bug in the man page, the behavior is documented in /usr/share/doc/less/README.Debian
).
In Debian and its derivatives (like Ubuntu) programs must use editor
as standard editor if neither $VISUIAL
nor $EDITOR
is set, see the Debian policy manual.
It's a documentation bug in the man page, the behavior is documented in /usr/share/doc/less/README.Debian
).
In Debian and its derivatives (like Ubuntu) programs must use editor
as standard editor if neither $VISUIAL
nor $EDITOR
is set, see the Debian policy manual.
answered Aug 17 at 13:13
Florian Diesch
62.7k16156176
62.7k16156176
Do you think I should create a Debian documentation bug for this or will that be ignored anyway in favor of more important bugs ?
– Juergen
Aug 17 at 13:44
Theless
package already contains a patch for the manpage so the maintainer seems to care about this kind of things.
– Florian Diesch
Aug 18 at 8:40
add a comment |Â
Do you think I should create a Debian documentation bug for this or will that be ignored anyway in favor of more important bugs ?
– Juergen
Aug 17 at 13:44
Theless
package already contains a patch for the manpage so the maintainer seems to care about this kind of things.
– Florian Diesch
Aug 18 at 8:40
Do you think I should create a Debian documentation bug for this or will that be ignored anyway in favor of more important bugs ?
– Juergen
Aug 17 at 13:44
Do you think I should create a Debian documentation bug for this or will that be ignored anyway in favor of more important bugs ?
– Juergen
Aug 17 at 13:44
The
less
package already contains a patch for the manpage so the maintainer seems to care about this kind of things.– Florian Diesch
Aug 18 at 8:40
The
less
package already contains a patch for the manpage so the maintainer seems to care about this kind of things.– Florian Diesch
Aug 18 at 8:40
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1066220%2fless-calls-nano-instead-of-vi%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password