From: plannine@sigint.cs.purdue.edu
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan9 so much easier than...
Date: Thu, 29 Jan 2009 16:45:22 -0500 [thread overview]
Message-ID: <20090129214522.GA1948@sigint.cs.purdue.edu> (raw)
In-Reply-To: <85e334c50901291204s788999dai4171f6987946e7e@mail.gmail.com>
On Thu, Jan 29, 2009 at 01:04:17PM -0700, Randall Bohn wrote:
> I needed to read a loose man file on Linux but couldn't remember how
> to format and display it.
>
> groff -man slig.8 wasn't readable.
>
> So I turned to drawterm.
>
> troff -man /mnt/term/home/bohn/slig.8 | page
>
> Problem solved.
Not to ruin a good story, but you can pass a file to Linux's man(1)
directly. e.g.:
$ man ./slig.8
Methinks that's even easier than using drawterm...
prev parent reply other threads:[~2009-01-29 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 20:04 Randall Bohn
2009-01-29 20:37 ` Pietro Gagliardi
2009-01-29 21:45 ` plannine [this message]
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=20090129214522.GA1948@sigint.cs.purdue.edu \
--to=plannine@sigint.cs.purdue.edu \
--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).