help / color / mirror / Atom feed
From: Matthew Singletary <matt.singletary@gmail.com>
To: discuss@mandoc.bsd.lv
Subject: Mandoc for oil
Date: Fri, 14 Jun 2019 04:16:17 -0400	[thread overview]
Message-ID: <CAAJ-tZJ=-8KHs4vOYhSZcaYA9tqLuOwUoLixHtZyekwDxjKb8w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 743 bytes --]

After seeing mandoc mentioned in the past, I thought I would look into
writing a man page for the Oil shell (http://www.oilshell.org/). I've never
written a man page before but thought I'd try to use some decent tools to
start with.

I'm a little confused about distribution/workflow for distributing man
pages (in general). If osh.1 is an mdoc flavored file, would that be used
(with mandoc -T man) to output a man page that could then be setup when Osh
is installed? Then how do you distinguish those? Oil uses autoconf for some
things, would that get tied into generating/installing the man pages on the

Sorry if these are dumb questions, but I'm not even sure what kind of
documentation I need to look through yet.


[-- Attachment #2: Type: text/html, Size: 921 bytes --]

             reply	other threads:[~2019-06-14  8:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  8:16 Matthew Singletary [this message]
2019-06-14  8:43 ` Jan Stary
2019-06-14  8:54   ` Jan Stary
2019-06-14  9:24     ` Matthew Singletary
2019-06-14 11:40       ` Jan Stary
2019-06-14 12:29       ` Ingo Schwarze
2019-06-14 13:08         ` Jan Stary
2019-06-14 14:27         ` Jan Stary
2019-06-14 14:54           ` Ingo Schwarze
2019-06-16  2:39             ` Matthew Singletary
2019-06-16 17:08               ` Ingo Schwarze
2019-06-14  9:54 ` Stephen Gregoratto
2019-06-14 12:03   ` Jan Stary

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAJ-tZJ=-8KHs4vOYhSZcaYA9tqLuOwUoLixHtZyekwDxjKb8w@mail.gmail.com' \
    --to=matt.singletary@gmail.com \
    --cc=discuss@mandoc.bsd.lv \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).