I need to use the less command with the syntax highlighting of the vim command for python, C, bash and other languages.
How do I apply syntax highlighting colors according to vim colors for less command?
asked Sep 17, 2013 at 6:17
Add a comment
|
5 Answers
Syntax highlighting of less, works just fine on most *nix systems.
apt install source-highlight
export LESSOPEN="| /usr/share/source-highlight/src-hilite-lesspipe.sh %s"
export LESS=' -R '
On Fedora/RedHat based distros use /usr/bin/src-hilite-lesspipe.sh instead.
Even on Cygwin you can do it with the minor adjustment of the shell script path and installing with apt-cyg instead of apt.
However, using this drastically slows down browsing of large files. I suggest to use alias in such a way to only implement the LESSOPEN export above when needed, like this:
alias lessh='LESSOPEN="| /usr/bin/src-hilite-lesspipe.sh %s" less -M '
where the -M flag is convenient to also show filename and line number.
Also remember to copy the script into your bin path:
cp /usr/share/source-highlight/src-hilite-lesspipe.sh /usr/bin/src-hilite-lesspipe.sh
UPDATE: 2019-07-24
Apparently, on more recent Cygwin installs, you have the following files in your path:
source-highlight.exe
source-highlight-esc.sh
source-highlight-settings.exe
So now you also need to execute the source-highlight-settings.exe that will add the configuration file:
$HOME/.source-highlight/source-highlight.conf.
-
1
-
-
3This worked for me on OSX: first I installed with:
brew install source-highlight, then I added an alias:alias lessh='LESSOPEN="| src-hilite-lesspipe.sh %s" less -R 'Aug 23, 2018 at 12:35
less doesn't support syntax highlighting.
vim, like all vi clones has a read-only mode called view which you can use to just view files. it supports all features of vim including syntax highlighting.
e.g.
view filename.py
the main difference between view and vi is that view doesn't "lock" the file you're viewing by creating a .swp file.
-
if your
view commandmeans fromradare package, it's not read only Sep 17, 2013 at 6:58 -
6Hmm, my
viewcommand doesn't seem to support syntax highlighting. I've tried:syntax enableand:syntax on, but I always getsyntax: Not an editor command. Myvimsupports highlighting, though.– FelixSep 17, 2013 at 10:14 -
@felix - do you have another
vilikenviorelvisinstalled? check your/usr/bin/view- on my debian system, it's a symlink to/etc/alternatives/viewwhich is, in turn, a symlink to/usr/bin/vim.basic.– casSep 17, 2013 at 10:29 -
1Hmm, in my case it's a symlink to
/usr/bin/ex, which, curiously, is owned by thevipackage.– FelixSep 17, 2013 at 10:35 -
2I can confirm what @Felix says, on
arch linuxviewis a symlink to/usr/bin/exofcore/vipackage.– x-yuriMay 16, 2015 at 16:51
I tend to disagree with Ingo, less can be taught to highlight syntax. Check out this answer on SuperUser. Basically, you have to install GNU's source-highlight (available in all major distro package repos), and then add the following to your .bashrc (or .bash_profile or what have you):
export LESSOPEN="| /path/to/src-hilite-lesspipe.sh %s"
export LESS=" -R "
However, note that source-highlight is not as powerful as vim's highlighter. Use whatever suits you best.
less cannot be taught to highlight syntax elements, but Vim can be used as a pager, i.e. a replacement for less. There are more advanced plugins, but the basic script actually ships with Vim ($VIMRUNTIME/macros/less.sh). For the full information, see Using vim as a syntax-highlighting pager on the Vim Tips Wiki.
answered Sep 17, 2013 at 8:32
-
3I'm surprised people doesn't even bother to Google before posting wrong answers... Jun 29, 2014 at 11:48
-
1@user1147688: If you carefully read Felix's answer, the GNU source-highlight is an external program, and the integration with less is very loose. It's not
lessthat does the highlighting; but Vim indeed has this capability built-in. Jun 29, 2014 at 11:59 -
3For the question "How do I apply syntax highlighting colors according to vim colors for less command?", the answer "By using source-highlight" seems like a more correct answer that "By using vim".– ZanoMar 10, 2015 at 9:21
-
3+1 but I'm sure what these comments are trying to say -- can't tell if they're even positive or negative ("...google before posting wrong answers"?, "installing xyz is more correct than just using vim"?). This answer is clearly the "most correct answer". Basically the OP didn't know this feature of vim existed, and this answer lets the OP know that it exists. Occam's razor ftw. The answer could only be improved by showing an example, e.g.,
$ diff file1.c file2.c | /usr/share/vim/vim74/macros/less.sh– michaelDec 5, 2016 at 2:51
After dabbling in some of the answers above, I think the most configuration-free solution is to just install and use vimpager.
It is available on github, homebrew, Arch (older version), AUR (latest), and maybe more.
After install you should be able to immediately use vimpager instead of less at your shell.
To utilise vimpager in other instances where less is used, you can change the PAGER variables your shell config (.bashrc etc.) by adding:
export PAGER=/usr/local/bin/vimpager
export MANPAGER=/usr/local/bin/vimpager
The install paths may (need to?) be different on OSX, but this works fine on Arch linux.
You can then set an alias to always substitute less for vimpager, in the same file:
alias less=$PAGER
(As described at the github readme)
