You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like the bat plain style, and my lesspipe is v2.04 from brew.
As far as I know, this is all good...but when I call less, it's not using bat at all. Just...something not colorful. I see something from lesspipe it looks like with the "append" message:
❯ less CHANGELOG.md==> append : to filename to view the markdown fileChangelogAll notable changes to this project will be documented in this file.The format is based on Keep a Changelog, and this project adheres toSemantic Versioning....
The weird thing is, I think I have pretty much the same settings on another laptop and it works. (Well, on that one I'm experimenting with using pygmentize, but still, I get color!).
Any ideas of my mistake?
The text was updated successfully, but these errors were encountered:
mathomp4
changed the title
Help with lesspipe
Help with lesspipe: no colorizing
Mar 14, 2022
The handling of the -l option for bat was slightly improved like in #77. The option for bat in the ENV variable LESSCOLORIZER is ignored. bat can be configured using ~/.config/bat/config.
LESS_ADVANCED_PREPROCESSOR is not used anymore.
Nevertheless I could not reproduce your problem, for me the files do show colors also with bat.
I apparently am an idiot as I can't figure out what I'm doing wrong.
So, I want to use
bat
to colorize with lesspipe. So, in my environment I have set:I like the
bat
plain style, and my lesspipe is v2.04 from brew.As far as I know, this is all good...but when I call
less
, it's not usingbat
at all. Just...something not colorful. I see something from lesspipe it looks like with the "append" message:The weird thing is, I think I have pretty much the same settings on another laptop and it works. (Well, on that one I'm experimenting with using
pygmentize
, but still, I get color!).Any ideas of my mistake?
The text was updated successfully, but these errors were encountered: