Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lnav reading from stdin (e.g. journalctl) prints input on exit #484

Closed
jefft opened this issue Dec 30, 2017 · 5 comments
Closed

lnav reading from stdin (e.g. journalctl) prints input on exit #484

jefft opened this issue Dec 30, 2017 · 5 comments

Comments

@jefft
Copy link

jefft commented Dec 30, 2017

For instance, run seq 100 | lnav. After quitting lnav, 1 to 100 printed on the terminal. lnav does not 'consume' stdin like, for instance, less or vim - does. It's a bit annoying having the whole log file dumped to the terminal.

@jefft
Copy link
Author

jefft commented Dec 30, 2017

Shell process substitution is a pretty decent workaround. e.g. lnav <(seq 100)

@tstack
Copy link
Owner

tstack commented Dec 30, 2017

The -q option should change the behavior.

@jefft
Copy link
Author

jefft commented Dec 30, 2017

lnav -q does the trick, thanks.

Hmm.. feels like -q should be the default, and scripts needing the current behaviour can end with write-to -. But then I don't understand the use-cases.

@jefft
Copy link
Author

jefft commented Jan 18, 2018

Duplicate of #436

@aspiers
Copy link
Contributor

aspiers commented Jul 28, 2019

Yes this is a duplicate; please close.

@jefft jefft closed this as completed Jul 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants