Skip to content

Have a non-pretty output thats usable from within scripts or piped tty #2484

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

Open
HeapUnderfl0w opened this issue Aug 25, 2019 · 1 comment
Labels

Comments

@HeapUnderfl0w
Copy link

User Story

I would like that lgsm supports some kind of output thats easily pipable or digestable by scripts. While the current way lgsm outputs information is pretty on a tty, systemd cannot
make sense of it.

Examples:

LGSM Output:
pretty lgsm output

What Systemd / journalctl displays:
systemd journalctl

Basic info

  • Distro: Any with SystemD
  • Game: Any
  • Command: monitor, others also applicable

Further Information

IMO there is 2 ways to do this.

  1. Detect if you are on a tty, and if not simply output all the information in a "non" pretty way, line by line
  2. Instead of detecting if you are on a tty give the user a command line switch to get the result.

Further Reading

At the moment i use this systemd service & timer to "monitor" every 6hrs.

( this is in relation to #2145 )

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label type: feature request to this issue, with a confidence of 0.95. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the type: feature request New feature or request label Aug 25, 2019
@HeapUnderfl0w HeapUnderfl0w changed the title Have a non-pretty output thats usable from within scripts or piped output Have a non-pretty output thats usable from within scripts or piped tty Aug 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants