For some period of time, I don't want to admit how long, less was first executing files and then actually opening them up.
Long story short, I saw my configuration for source highlight was clobbered, instead of:
It was:
I was able to trace the problem back to a large refactor I did for all of my 'apps' programming in shell
. I moved from a separate git repository into a monolith repository so I could more easily share libraries across these 'apps' when they're 'compiled'. At the same time, I renamed configuration keys and essentially, when this was set, the configuration key it was pointing to didn't exist.
This perhaps nothing to do with less, but more rather how users (myself) can easily shoot themselves in the foot quickly and possibly do damage unintentionally.
Well, at least now again, I can now view color-coded source code without less trying to execute it first.
Long story short, I saw my configuration for source highlight was clobbered, instead of:
Code:
export LESSOPEN="| /usr/local/bin/src-hilite-lesspipe.sh %s"
export LESS=" -R "
It was:
Code:
export LESSOPEN="| %s"
export LESS=" -R "
I was able to trace the problem back to a large refactor I did for all of my 'apps' programming in shell
This perhaps nothing to do with less, but more rather how users (myself) can easily shoot themselves in the foot quickly and possibly do damage unintentionally.
Well, at least now again, I can now view color-coded source code without less trying to execute it first.