Add a man page on the rules format

[bradlarsen]

Nosey Parker now has auto-generated manpages for its command-line interface (#88). It would also be helpful if there were a manpage on the rules and rulesets format used by Nosey Parker.

This manpage probably belongs in section 5 (the one for file formats).

This manpage is not something that would be auto-generated. Using the existing RULES.md documentation that I keep forgetting about would be a good starting point.

The manpage should be included in prebuilt Nosey Parker releases.

[munntjlx]

I can volunteer to help. Just guide me.

Thomas

[bradlarsen]

@munntjlx I'm not sure about formatting of a handwritten manpage. I'm actually not familiar with the syntax that man / nroff uses. My preference based purely on familiarity would be to try to convert Markdown into a manpage, but I'm not dead-set on that.

I think the starting point is to look at the content of the existing RULES.md page. I wrote that a long time ago, and as the author, don't always have a great sense for what is not clear about it. So any feedback, questions, or expansions you have on that would be valuable.

[munntjlx]

Maybe a pandoc macro that coverts a specifically formatted md to an appropriate man page?

…

________________________________________ From: Brad Larsen ***@***.***> Sent: Wednesday, 27 March 2024 15:39 To: praetorian-inc/noseyparker Cc: Munn, Thomas (LNG-RDU); Mention Subject: Re: [praetorian-inc/noseyparker] Add a man page on the rules format (Issue #141) *** External email: use caution *** @munntjlx<https://github.com/munntjlx> I'm not sure about formatting of a handwritten manpage. I'm actually not familiar with the syntax that man / nroff uses. My preference based purely on familiarity would be to try to convert Markdown into a manpage, but I'm not dead-set on that. I think the starting point is to look at the content of the existing RULES.md<https://github.com/praetorian-inc/noseyparker/blob/main/docs/RULES.md> page. I wrote that a long time ago, and as the author, don't always have a great sense for what is not clear about it. So any feedback, questions, or expansions you have on that would be valuable. — Reply to this email directly, view it on GitHub<#141 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALVIUB3HBK6GZFIDPDUMPITY2MOAFAVCNFSM6AAAAABELYUJX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRTHAZDIOBVGY>. You are receiving this because you were mentioned.Message ID: ***@***.***>