canlock-mhp(1)

💌 canlock-mhp — bestie's guide to the message header parser

okay so real quick — this page lives in the canlock-hp 3.3.2 manual, and it's literally just the CLI frontend for the libcanlock library. that's the whole vibe. let's get into it 🫶

---

✨ NAME ✨

canlock-mhp — CLI frontend for libcanlock library. yes that's it, that's the whole name section, she's short and she knows it 💅

---

🌸 SYNOPSIS 🌸

canlock-mhp -h | -v

canlock-mhp -f fieldname

two modes, no in-between. help/version girlie, or field-name girlie. pick your fighter 🎀

---

🦋 DESCRIPTION 🦋

Message Header Parser (mhp) for RFC5536 conformant Netnews articles. that's the official job title, put some respect on it 👑

The name of a single header field must be specified with the -f option. one field. singular. not a buffet, bestie 🙈

The message in canonical format (with US-ASCII encoded CRLF line breaks) is read from stdin. and here's the part people always trip on — if your message is in some local format (e.g. EBCDIC encoded or with LF line breaks), it must be converted to canonical format before it can be used as input. like, you gotta do the conversion yourself, this tool is not your converter, she is a parser 💀

The input data may be a naked header without message body, but the empty line separator after the header must always be present. don't skip the blank line. the blank line is the moment, the blank line is the main character. 😭

The syntax of the extracted header field is not checked beyond the folding. so don't come here expecting full validation, she's not doing that. The rest of the message need not be fully RFC5536 conformant too, as long as all header fields start on new lines (and are correctly folded, so that there is no ambiguity). Common syntax errors (like 8-bit characters in the header) are ignored. lowkey forgiving, highkey iconic ✨

If the specified header field is found, it is extracted, unfolded and printed to stdout (without trailing line break). no trailing newline. nope. not even one. 🎀

If there are multiple header fields with the specified name, the first one is used. first come, first served, that's the rule 🏁

---

💅 OPTIONS 💅

The following options are supported:

• -f fieldname — Specify the header field name to search for (without the colon). no colon, bestie, leave the colon at home 🚫
• -h — Print help message, then exit. the classic "what does anything do" button 🫶
• -v — Print version and compile time options, then exit. compile time options!! she's showing off her build config, we love a transparent queen 👑

---

🔥 EXIT STATUS 🔥

Zero on success or regular exit respectively. All other values indicate an error.

so like, 0 = slay, anything else = something went sideways 😭

---

💖 AUTHORS 💖

Michael Baeuerle — the icon, the legend, the author 🫡

---

🌈 REPORTING BUGS 🌈

Report bugs to <mailto:michael.baeuerle@gmx.net>. found a bug? email it, don't just vague-post about it 💌

---

⭐ STANDARDS ⭐

canlock-mhp tries to comply with the following standards:

• RFC 5536

"tries to" — we respect the honesty ngl 🧚

---

🍓 SEE ALSO 🍓

• canlock-hfp(1)
• canlock(1)

go read those too, the lore is deep iykyk 📚

---

heads up bestie: remember the empty line after the header. i'm not kidding. it's non-negotiable. the blank line is load-bearing 💀

---

okay and finally, the cute sign-off: this page is from the Unix corner of the world, dated 2024-05-11, and yes she's serving vintage-but-current. periodt. 🎀✨🦋