MANCHA(1)

πŸ“¦
version 0.5.0 Β· 2 versions
, in alpine 3.24, arch rolling, nixpkgs unstable, ubuntu stonking

πŸ’– MANCHA(1) πŸ’–

okay bestie, welcome to <rainbow>MANCHA</rainbow> β€” she lives in section 1 of your General Commands Manual and she's literally the moment. πŸŽ€


✨ NAME ✨

mancha β€” view manual pages via cha(1)


🌸 SYNOPSIS 🌸

mancha [-M path] [section] name
mancha [-M path] [section] -k keyword
mancha -l file

πŸ¦‹ DESCRIPTION πŸ¦‹

so mancha lets you read man pages inside the Chawan browser. it's giving w3mman(1) energy, fr fr β€” same concept, different era. πŸ’…

what she actually does: she runs cha(1) with the right man:, man-k: or man-l: URL, and then the protocol adapter opens the man page and injects markup into it. so like, man page references become man: links. hyperlinks but make it manpages. iconic behavior, no cap. ✨


πŸ’… OPTIONS πŸ’…

here are the command line options, bestie, all three of them, obsessed:

  • -M path β€” sets path as the MANPATH environment variable. if you wanna know exactly how that gets interpreted, go check man(1), she explains it. πŸ”
  • -k keyword β€” uses keyword to do a keyword-based man page search. basically the flow where you're like "i don't remember the command name, i just remember the vibe" 😭
  • -l file β€” opens the local file you specify as a man page. πŸ“

🌈 ENVIRONMENT 🌈

these environment variables are in the mix:

  • MANCHA_CHA β€” if it's set, whatever's inside it gets used instead of cha. quick note though: the cha command is called through system(3), so honestly you do not have to override it as long as cha is chillin' somewhere in your PATH. 🫢
  • MANCHA_MAN β€” if it's set, its contents get used instead of /usr/bin/man.
  • MANCHA_APROPOS β€” if it's set, its contents get used instead of /usr/bin/man.
okay so. yes. MANCHA_APROPOS also says /usr/bin/man up there. this is not a typo β€” the original page says it that way and we are NOT fixing it, we're respecting it. πŸ’€

so here's the tea on that: normally (except on FreeBSD), mancha assumes that man(1) is compatible with apropos(1) and that it accepts the -s parameter. so overriding MANCHA_MAN also overrides the command used for man-k β€” but only as long as MANCHA_APROPOS is not set. periodt. πŸ‘‘


πŸ’œ SEE ALSO πŸ’œ

man(1), cha(1), cha-cgi(5), w3mman(1)


okay that's the whole page, you ate it, you're the main character now πŸ§šπŸ’– little sign-off for you: this was <rainbow>MANCHA(1)</rainbow> from the General Commands Manual, and the footer just says MANCHA(1) back at you like a lil mirror. bye bestie, go read some manual pages πŸŒŸπŸ’œ

πŸ“¦ where this page comes from