Skip to content

parsing cli tables #31

@slavaGanzin

Description

@slavaGanzin

Hello, Abhimanyu. Awesome tool.

I used eat before and I want to switch to sttr, because of more general use cases covered by it, and because it's a single binary cli. Checks all the boxes.

What I do a lot with eat is parsing standard CLI tables like ps or docker images:

$ ps | eat

[
  {
    "PID": "5424",
    "TTY": "pts/1",
    "TIME": "00:00:00",
    "CMD": "fish"
  },
  {
    "PID": "6183",
    "TTY": "pts/1",
    "TIME": "00:00:00",
    "CMD": "ps"
  },
  {
    "PID": "6184",
    "TTY": "pts/1",
    "TIME": "00:00:00",
    "CMD": "node"
  },
  {
    "PID": "6185",
    "TTY": "pts/1",
    "TIME": "00:00:00",
    "CMD": "xclipm"
  }
]

I use this as a preprocessing step before manipulating data with something like jq or fx

Actually, I implemented this in eat. Code is super easy, but it works.
antonmedv/eat@0c2bec8#diff-e727e4bdf3657fd1d798edcd6b099d6e092f8573cba266154583a746bba0f346R79-R81

Maybe you could look into it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions