9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Aharon Robbins <arnold@skeeve.com>
To: 9fans@9fans.net
Subject: Re: [9fans] formatting the manual from plan9 ports?
Date: Tue, 29 May 2012 23:46:50 +0300	[thread overview]
Message-ID: <201205292046.q4TKkoqZ010156@skeeve.com> (raw)
In-Reply-To: <CAOe8CcYPYZ257WEdQiQCyKmfj+XWOjqoo5TU-=j4By9NAfSwYQ@mail.gmail.com>

Hi.

Thanks. I did see that. I was wondering more about all the hardcoded
path names in the various scripts in /sys/man and /sys/lib/man and
also getting p9p mk to use rc instead of sh to run commands.

I suppose that I will just manually "nerd through it" (as a friend
used to say).

Thanks,

Arnold

> From: pmarin <pmarin.mail@gmail.com>
> Date: Fri, 25 May 2012 21:08:18 +0200
> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
> Subject: Re: [9fans] formatting the manual from plan9 ports?
>
> See the example in tr2post(1)
>
> On Thu, May 24, 2012 at 9:03 PM, Aharon Robbins <arnold@skeeve.com> wrote:
> > Is there a simple recipe to use p9p troff to format the manual pages
> > from the plan 9 dist? ??I.e.:
> >
> > ?? ?? ?? ??Install Plan 9 Ports
> > ?? ?? ?? ??wget plan9.iso from bell labs
> > ?? ?? ?? ??mount said iso /some/where
> > ?? ?? ?? ??9 rc
> > ?? ?? ?? ??cd /some/where/sys/man
> > ?? ?? ?? ??# magic stuff here
> >
> > (Or tar off the dist to regular files where things are writable.)
> >
> > Thanks!
> >
> > Arnold



  reply	other threads:[~2012-05-29 20:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 19:03 Aharon Robbins
2012-05-25 19:08 ` pmarin
2012-05-29 20:46   ` Aharon Robbins [this message]
2012-05-29 21:05     ` erik quanstrom
2012-05-30  3:44     ` cinap_lenrek
2012-05-30  4:03       ` erik quanstrom
2012-05-30  6:11 arnold
2012-05-30 12:38 ` erik quanstrom

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=201205292046.q4TKkoqZ010156@skeeve.com \
    --to=arnold@skeeve.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).