Since I do not have a C or C++ build environment, I was looking for the less 530 release for Windows.
I found it via these links:
- [WayBack] Less FAQ
- [WayBack] Less version history
- [WayBack] Downloading less
- win32 version 530 in [Archive.is] Index of /misc/less
- version 530 [WayBack] less: README | Fossies
- [WayBack] GitHub – gwsw/less: Less – text pager
- Stuck at 530: [WayBack] GitHub – rivy/less
Searching for less 530, I bumped in these links as well:
- [WayBack] `less` performs differently when invoked from Bash and from Git – Unix & Linux Stack Exchange
- When invoked via
git, it does not restore screen content
- When invoked via
- Cause: [WayBack] Git – git-config Documentation:
core.pager
core.pager
Text viewer for use by Git commands (e.g., less). The value is meant to be interpreted by the shell. The order of preference is the
$GIT_PAGERenvironment variable, thencore.pagerconfiguration, then$PAGER, and then the default chosen at compile time (usually less).When the
LESSenvironment variable is unset, Git sets it toFRX(ifLESSenvironment variable is set, Git does not change it at all). If you want to selectively override Git’s default setting forLESS, you can setcore.pagerto e.g.less -S. This will be passed to the shell by Git, which will translate the final command toLESS=FRX less -S. The environment does not set theSoption but the command line does, instructing less to truncate long lines. Similarly, settingcore.pagertoless -+Fwill deactivate theFoption specified by the environment from the command-line, deactivating the “quit if one screen” behavior ofless. One can specifically activate some flags for particular commands: for example, settingpager.blametoless -Senables line truncation only forgit blame.Likewise, when the
LVenvironment variable is unset, Git sets it to-c. You can override this setting by exportingLVwith another value or settingcore.pagertolv +c.
–jeroen
The Wiert Corner - irregular stream of stuff 