[birchb]

Author here: Often I have to digest log files and lists of Azure resource names. I prefer to work with hierarchies of things, so I wrote this simple filter. Turns out to quite handy, especially when combined with awk and its friends.

[jarmitage]

Great, very handy! Just FYI `readlink -f` doesn't work on macOS

May I suggest the name txtree?

[birchb]

Sorry macos people, I don't own an Apple. (Not strictly true, I have an iMac rescued from a dumpster, but it's running Ubuntu now). Apparently greadlink is available https://stackoverflow.com/a/4031502 for you.

[jedberg]

Very cool tool! Any chance that you're going to add it to Homebrew?

[eevilspock]

https://github.com/birchb1024/frangipanni/issues/2

[birchb]

Mac binary https://github.com/birchb1024/frangipanni/releases/download/...

[birchb]

I refer you to the answer I gave earlier.

[inadequatespace]

Ah yes, I was just thinking that this could be useful for `aws s3 ls` and similar.

(Really I just want `tree` on `s3`. There's `s3-tree` but that uses the entire bucket rather than a prefix)

[clankyclanker]

I love this as a post-processor for log-files. We actually have something like this at work. Unfortunately, it's applied to log-files by default. It's terrible: it breaks grep, and I haven't been able to figure a way around that.

Have you found any solutions for grepping on matching lines? Presumably, one could use awk, but awk takes a lot of cycles.

[birchb]

Grepping the _input_ is, like, Standard. Knowhatimean bruv?