On Sat, 15 May 1999, Lars Wirzenius wrote:
Othmar Pasteka [EMAIL PROTECTED]:
Actually you can make some text output with groff, for instance:
groff -man -Tascii pon.1 pon.txt
Yes, of course. The point raised earlier by this thread is that groff
takes lots of space. The programs I pointed
Bradley Bell wrote:
Here, for example, is a teeny tiny little nroff that does a good job
reading most, but not all man pages:
ftp://metalab.unc.edu/pub/Linux/utils/text/nroffsrc.tar.Z
I'll have to check this out. If anyone is thinking about implementing
a short 'man' shell script to go with
Hi, I just joined the list and missed the beginning of the thread, but I
generally use man2html in a cron job and have a shell cgi do a find in the
htdocs area from my apache site when I get a little confused...
Most of my stuff is perl anyway, being C illiterate, so I also do a lot of
Hi,
Actually you can make some text output with groff, for instance:
groff -man -Tascii pon.1 pon.txt
works for me :). Let's say for the manuals, but works.
so long
Othmar
Lars Wirzenius wrote:
Manual pages are actually written in a new language, defined
using the troff macro language. It is much simpler than the
real troff language.
This may no longer be true. I see quite a few codes in manpages
that aren't defined by man(7). For example, the manpage for [
On 13-May-99 Bradley Bell wrote:
has anybody thought about packaging an alternative to the man-db/groff
combination for reading man pages? 4mb is a lot for small systems, and
reading man pages is pretty much a neccessity.
Maybe I am wrong here but, how else are you gonna do it? man pages
On Thu, May 13, 1999 at 11:17:57PM -0400, Shaleh wrote:
:
: On 13-May-99 Bradley Bell wrote:
: has anybody thought about packaging an alternative to the man-db/groff
: combination for reading man pages? 4mb is a lot for small systems, and
: reading man pages is pretty much a neccessity.
:
:
7 matches
Mail list logo