What is the difference between the two commands below?
more file-name
less file-name
When you use the command journalctl -p err -b for example, you get an answer that ends with "END". What command do I use to end this and get the opportunity to enter the next command without having to close the window and open a new one?
erik@server ~ $ journalctl -p err -b
-- Logs begin at sön 2019-09-22 20:17:42 CEST, end at sön 2019-09-22 20:20:01 CE
sep 22 20:17:51 server iscsid[1289]: iSCSI daemon with pid=1290 started!
lines 1-2/2 (END)
As in the title. Neither dpkg -S /usr/bin/less nor apt-file search /usr/bin/less produces anything useful.
Does it mean that there's a bug or that less really doesn't come from any package?
(In case you're wondering why I need to know the answer, I find that the less is an old version 487 instead of 530 that has a feature I want.)
$ which less
/usr/bin/less
$ dpkg -S /usr/bin/less
dpkg-query: no path found matching pattern /usr/bin/less
$ apt-file search /usr/bin/less
colorized-logs: /usr/bin/lesstty
libcss-lessp-perl: /usr/bin/lessp
node-less: /usr/bin/lessc
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) ?
Every time I search for a term in less, it stores my search in the file .lesshst. How can I stop this behavior?