SC_WARTSDUMP(1)

πŸ’– sc_wartsdump β€” bestie edition πŸ’–

okay so this is sc_wartsdump, a lil tool from the General Commands Manual section (that's section 1, user commands, iykyk) and she is literally here to spill everything inside your warts files. ✨


🌸 NAME 🌸

sc_wartsdump β€” verbose dump of information contained in a warts file.

like. verbose verbose. she does not hold back. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

sc_wartsdump [file ...]

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does she actually do?? sc_wartsdump gives you a verbose dump of all the info chillin' inside a sequence of warts files. feed her one, feed her many, she'll go through them one by one. 🌈

now here's the tea you need to hear, bestie, and I need you to actually listen:

the output is structured and totally fine for doing some first-pass eyeballing of your results, but the format is NOT suitable for automated parsing and analysis. and why?? because the output of sc_wartsdump will change over time with no regard to backwards compatibility. no cap. she said what she said. 😭

so if you're out here tryna build a pipeline that parses this output, don't. if you actually need to analyse the contents of a warts file, do it the correct way: use specialised programs which link against the scamper file API. that's the move. that's the assignment. πŸ‘‘


✨ EXAMPLES ✨

okay demo time, let's go 🫢

the command:

sc_wartsdump file1.warts file2.warts

will decode and print the contents of file1.warts, followed by the contents of file2.warts. one after the other, in order, no drama. πŸ’œ

and this one?? this one is my fave:

gzcat file1.warts.gz | sc_wartsdump

this will print the contents of the uncompressed file supplied on stdin. piping queen behaviour honestly. 🌸


πŸ‘‘ SEE ALSO πŸ‘‘


πŸ’œ AUTHORS πŸ’œ

sc_wartsdump was written by Matthew Luckie <mjl@luckie.org.nz>. icon behaviour, we love to see it. πŸŽ€


Debian shipped this one on October 15, 2010, and that's the whole manual bestie β€” now go dump some warts, you absolute legend. πŸ’…βœ¨πŸ¦‹