Minor bug but it's an annoying one. May even be a design decision. journalctl -a should prevent long lines of output from being truncated. It only works that way when coupled with --no-pager or redirected to a file, so 'journalctl -a --no-pager | less' or 'journalctl -a > journal.txt'. Reproducible: Steps to Reproduce:
journalctl -a --no-pager | less and journalctl -a both behave the same to me. Lines are not wrapped, but they are not truncated either (you use right+left on the keyboard to scroll horizontally). Am I missing the problem?
Ahh operator error in that case Colin. To think after all this time it never crossed my mind to use left/right cursor keys :\ The wrap missing is the difference that confused me. Copying text from the built in pager, without wrap, cuts off extraneous text. Close as a meatware bug if you like :)
The non-wrapping and scrolling is to do with the default pager settings but you can override with a env var SYSTEMD_PAGER. That said there does seem to be a bug... By default our pager settings are "less -FR" and doing "journalctl -a -b" indeed creates a process accordingly but *does not* wrap the lines. But if we do "journalctl -a -b | less -FR" it *does* wrap the lines. So yeah, I think there is a bug in there somewhere. I also cannot reproduce my behaviour from above and I *do* see a difference between the two commands (they are wrapped by default when doing an out of process less)
I'm glad it's been a useful exercise at least Colin, thanks for looking into it and responding so quickly :)
I gather this is OK to close?
Status: NEW => RESOLVEDCC: (none) => nicResolution: (none) => FIXED