> Alexis writes:
> * Should ledger really be looking for and use less if PAGER is unset? Isn't
> the absence of PAGER and indicator that the user prefers their output
> straight to the terminal?
I don’t think it should. If PAGER is not set, it shouldn’t use a pager…
> * When looking for
Thanks John for providing support and thanks for raising this issue Bob.
Looking at the code there are few questions that arise for me:
* Should ledger really be looking for and use less if PAGER is unset?
Isn't the absence of PAGER and indicator that the user prefers their
output straight to
> "BW" == Bob Wilson writes:
BW> --no-pager works. Terminology in hand, the guide suggested looking at the
BW> LEDGER_PAGER environment variable, which is unset on my platform.
BW> I installed via homebrew (I'm on macos 13.4). Perhaps some detail on how
BW> they compiled ledger is relevant?
--no-pager works. Terminology in hand, the guide suggested looking at the
LEDGER_PAGER environment variable, which is unset on my platform.
I installed via homebrew (I'm on macos 13.4). Perhaps some detail on how
they compiled ledger is relevant?
On Friday, June 9, 2023 at 11:36:04 PM UTC-7
> "BW" == Bob Wilson writes:
BW> Previously, running a command like `ledger -f ledger.dat balance ^ Assets`
BW> would print results directly to the screen and return me to the prompt,
BW> but now that same command prints results to some kind of temporary screen
BW> that disappears when I hit
Hi folks,
I recently upgraded to Ledger 3.3.2-20230330, from 3.2.1-20200518.
Previously, running a command like `ledger -f ledger.dat balance ^Assets`
would print results directly to the screen and return me to the prompt, but
now that same command prints results to some kind of temporary
