On Tuesday, December 06, 2022 09:53:11 AM Richard Owlett wrote:
> It worked acceptabily on Debian 9.13 . I have to read manual to see if I
> can make a cosmetic tweak.
If you describe the cosmetic tweak you need, I (or someone else) *might* be
able to help.
--
rhk
If you reply: snip, snip, and
Richard Owlett wrote:
rhkra...@gmail.com wrote:
On Tuesday, December 06, 2022 07:01:07 AM Richard Owlett wrote:
I just tried it on both of my machines.
It lacks ability to set the right margin. I want to insert a paragraph
such that the effective LEFT margin [when line wraps at RIGHT margin] is
rhkra...@gmail.com wrote:
On Tuesday, December 06, 2022 07:01:07 AM Richard Owlett wrote:
I just tried it on both of my machines.
It lacks ability to set the right margin. I want to insert a paragraph
such that the effective LEFT margin [when line wraps at RIGHT margin] is
the indent level.
Ju
On Tuesday, December 06, 2022 07:01:07 AM Richard Owlett wrote:
> I just tried it on both of my machines.
> It lacks ability to set the right margin. I want to insert a paragraph
> such that the effective LEFT margin [when line wraps at RIGHT margin] is
> the indent level.
Just as a followup to my
On Tuesday, December 06, 2022 07:01:07 AM Richard Owlett wrote:
> I just tried it on both of my machines.
> It lacks ability to set the right margin. I want to insert a paragraph
> such that the effective LEFT margin [when line wraps at RIGHT margin] is
> the indent level.
I started to write a rat
Richard Owlett wrote:
Andreas Rönnquist wrote:
On Sun, 4 Dec 2022 05:29:58 -0600,
Richard Owlett wrote:
I wish to document a personal project.The desired format will resemble
the outline for term papers we wrote in school in the 50's. Except
some items may be a short paragraph or two long.
I
Richard Owlett wrote:
Andreas Rönnquist wrote:
On Sun, 4 Dec 2022 05:29:58 -0600,
Richard Owlett wrote:
I wish to document a personal project.The desired format will resemble
the outline for term papers we wrote in school in the 50's. Except
some items may be a short paragraph or two long.
I
Andreas Rönnquist wrote:
On Sun, 4 Dec 2022 05:29:58 -0600,
Richard Owlett wrote:
I wish to document a personal project.The desired format will resemble
the outline for term papers we wrote in school in the 50's. Except
some items may be a short paragraph or two long.
I did a web search for te
On 12/4/22 03:29 AM, Richard Owlett wrote:
I wish to document a personal project.The desired format will resemble
the outline for term papers we wrote in school in the 50's. Except
some items may be a short paragraph or two long.
I did a web search for text editors with an auto-indent feature.
On Sun, 4 Dec 2022 05:29 -0600, Richard Owlett wrote:
> I wish to document a personal project.The desired format will resemble
> the outline for term papers we wrote in school in the 50's. Except some
> items may be a short paragraph or two long.
Like some others here, I can only guess what thos
On 2022-12-04, David Wright wrote:
> On Sun 04 Dec 2022 at 05:29:58 (-0600), Richard Owlett wrote:
>> I wish to document a personal project.The desired format will resemble
>> the outline for term papers we wrote in school in the 50's. Except
>> some items may be a short paragraph or two long.
>
>
On Sun, 4 Dec 2022 05:29:58 -0600,
Richard Owlett wrote:
>I wish to document a personal project.The desired format will resemble
>the outline for term papers we wrote in school in the 50's. Except
>some items may be a short paragraph or two long.
>
>I did a web search for text editors with an auto
On Sun 04 Dec 2022 at 05:29:58 (-0600), Richard Owlett wrote:
> I wish to document a personal project.The desired format will resemble
> the outline for term papers we wrote in school in the 50's. Except
> some items may be a short paragraph or two long.
Tragically I missed out on a US education,
On Sun, 4 Dec 2022 12:56:57 +
"Andrew M.A. Cater" wrote:
> Might I suggest gedit or similar. Or even emacs or vim :)
In Emacs' case (and probably in vim's) there may well be a mode that
will do what the OP wants. Text mode will maintain auto-indentation for
you. Also, look into outline mode
On 2022-12-04 at 07:56, Andrew M.A. Cater wrote:
> On Sun, Dec 04, 2022 at 05:29:58AM -0600, Richard Owlett wrote:
>
>> I wish to document a personal project.The desired format will
>> resemble the outline for term papers we wrote in school in the
>> 50's. Except some items may be a short paragra
On 4/12/22 20:56, Andrew M.A. Cater wrote:
On Sun, Dec 04, 2022 at 05:29:58AM -0600, Richard Owlett wrote:
I wish to document a personal project.The desired format will resemble the
outline for term papers we wrote in school in the 50's. Except some items
may be a short paragraph or two long.
On Sun, Dec 04, 2022 at 05:29:58AM -0600, Richard Owlett wrote:
> I wish to document a personal project.The desired format will resemble the
> outline for term papers we wrote in school in the 50's. Except some items
> may be a short paragraph or two long.
>
> I did a web search for text editors w
I wish to document a personal project.The desired format will resemble
the outline for term papers we wrote in school in the 50's. Except some
items may be a short paragraph or two long.
I did a web search for text editors with an auto-indent feature.
The only one I recognized was Leafpad. But
1 17:17:53 Greg Wooledge wrote:
> > >
> > > [...]
> > >
> > > > > We still don't know why you want this. I guess we'll never
> > > > > know.
> > > >
> > > > We apparently don't speak the same dialect of englis
3 Greg Wooledge wrote:
> >
> > [...]
> >
> > > > We still don't know why you want this. I guess we'll never know.
> > >
> > > We apparently don't speak the same dialect of english Greg. I wanted
> > > a dead tree (aka paper) copy of a manpage, with ALL th
gt; > > > We still don't know why you want this. I guess we'll never know.
> > >
> > > We apparently don't speak the same dialect of english Greg. I wanted
> > > a dead tree (aka paper) copy of a manpage, with ALL the markup
> > > totally
>
> > We apparently don't speak the same dialect of english Greg. I wanted
> > a dead tree (aka paper) copy of a manpage, with ALL the markup
> > totally stripped. As for Lee's suggestion, I didn't try it since
> > Cindy's example worked perfectly
On Sat 02 Oct 2021 at 16:51:59 +0100, Eric S Fraga wrote:
> On Saturday, 2 Oct 2021 at 15:39, Brian wrote:
> > BTW, I do not think gv accepts an output piped to it.
>
> Well, it does on my Debian system. YMMV, of course.
>
> I did try the command before posting. ;-)
Eyesight. Many apologies.
On Saturday, 2 Oct 2021 at 15:39, Brian wrote:
> BTW, I do not think gv accepts an output piped to it.
Well, it does on my Debian system. YMMV, of course.
I did try the command before posting. ;-)
--
Eric S Fraga via Emacs 28.0.60 & org 9.5 on Debian 11.0
On Saturday, 2 Oct 2021 at 09:03, Greg Wooledge wrote:
> This appears to produce a Postscript stream.
Yes; I was basing my post on the specified need for "dead wood" output.
--
Eric S Fraga via Emacs 28.0.60 & org 9.5 on Debian 11.0
nted a
> dead tree (aka paper) copy of a manpage, with ALL the markup totally
> stripped. As for Lee's suggestion, I didn't try it since Cindy's example
> worked perfectly and by the time I read Lee's msg, I had what I needed
> on the output tray of my huge printer.
On Sat 02 Oct 2021 at 09:03:39 -0400, Greg Wooledge wrote:
> On Sat, Oct 02, 2021 at 12:45:07PM +0100, Eric S Fraga wrote:
> > man pages are written in troff/nroff (which can be compiled using groff)
> > using the man style. You can do the following, for instance:
> >
> > gunzip -c /usr/share/ma
On Sat, Oct 02, 2021 at 12:45:07PM +0100, Eric S Fraga wrote:
> man pages are written in troff/nroff (which can be compiled using groff)
> using the man style. You can do the following, for instance:
>
> gunzip -c /usr/share/man/man1/chmod.1.gz | groff -man | lp
>
> (or replace "lp" with "gv -"
searching the whole database, as there might be duplicate names to
> confuse the issue, but it this case look in man/man9 for the requested
> manpage. Sheesh, doesn't anyone read manpages anymore? :o)
> [...]
In Debian's man command, if there are two arguments given, the first
ar
On Saturday 02 October 2021 07:45:07 Eric S Fraga wrote:
> man pages are written in troff/nroff (which can be compiled using
> groff) using the man style. You can do the following, for instance:
>
> gunzip -c /usr/share/man/man1/chmod.1.gz | groff -man | lp
>
> (or replace "lp" with "gv -" to see
man pages are written in troff/nroff (which can be compiled using groff)
using the man style. You can do the following, for instance:
gunzip -c /usr/share/man/man1/chmod.1.gz | groff -man | lp
(or replace "lp" with "gv -" to see on screen).
Replace chmod with specific command and note that ther
s a well-known command named "9"),
> so I used man man and man bash¹.
There is a well known man 9 command, it means to save man the trouble of
searching the whole database, as there might be duplicate names to
confuse the issue, but it this case look in man/man9 for the reque
ers, whereas the first one has no tabs at all -- only spaces.
>
> So I guess most (or all?) of the size reduction is groups of spaces
> being replaced by tabs.
The manpage is jogaxisget.9. and they look very close to identical, but
an ls -l shows:
-rw-r--r-- 1 pi pi1321 Oct 2
On Friday 01 October 2021 20:44:41 Fred wrote:
> On 10/1/21 1:59 PM, Gene Heskett wrote:
> > On Friday 01 October 2021 12:34:16 Larry Martell wrote:
> >
> > man -t /path/to/man/file >file.txt
> > groff -mandoc /path/to/man/file > file.txt, both quadrupled the size
> > with lots more markup.
> >
>
On Fri 01 Oct 2021 at 20:53:26 (-0400), Greg Wooledge wrote:
> On Fri, Oct 01, 2021 at 05:44:41PM -0700, Fred wrote:
> > man command | col -b > command.txt
>
> Curious.
>
> unicorn:~$ man ls > ls1
> unicorn:~$ man ls | col -b > ls2
> unicorn:~$ ls -l ls1 ls2
> -rw-r--r-- 1 greg greg 8299 Oct 1 2
On Fri, Oct 01, 2021 at 05:44:41PM -0700, Fred wrote:
> man command | col -b > command.txt
Curious.
unicorn:~$ man ls > ls1
unicorn:~$ man ls | col -b > ls2
unicorn:~$ ls -l ls1 ls2
-rw-r--r-- 1 greg greg 8299 Oct 1 20:49 ls1
-rw-r--r-- 1 greg greg 7745 Oct 1 20:49 ls2
Glancing at the diff -u
On 10/1/21 1:59 PM, Gene Heskett wrote:
On Friday 01 October 2021 12:34:16 Larry Martell wrote:
man -t /path/to/man/file >file.txt
groff -mandoc /path/to/man/file > file.txt, both quadrupled the size with
lots more markup.
Not what I want obviously.
Thanks Larry.
Cheers, Gene Heskett.
man c
:09 manls
> -rw-r--r-- 1 greg greg 8299 Oct 1 17:10 manls2
> unicorn:~$ cmp manls manls2
> unicorn:~$
>
>
> We still don't know why you want this. I guess we'll never know.
We apparently don't speak the same dialect of english Greg. I wanted a
dead tree (aka pap
On Fri, Oct 01, 2021 at 05:21:54PM -0400, Gene Heskett wrote:
> What I wanted on dead tree, was exactly what I see on screen.
> With the manpage markup gobbled up, leaving only the text I see on screen
> when I type man 9 filename.
So you wanted to print a man page on paper, but you
ile.txt, both quadrupled the size
> > with lots more markup.
> >
> > Not what I want obviously.
>
> There is nothing obvious here. What do you want? Why? What are you
> going to do with the resulting file(s)?
What I wanted on dead tree, was exactly what I see on screen.
On Friday 01 October 2021 15:47:18 Greg Wooledge wrote:
> On Fri, Oct 01, 2021 at 12:24:50PM -0400, Gene Heskett wrote:
> > With the man markup subtracted, so what we save is exactly what we
> > see.
>
> If you want to reproduce what you see when you type "man bash" (just
> as an example), you wou
On Fri, Oct 01, 2021 at 05:05:44PM -0400, Gene Heskett wrote:
> On Friday 01 October 2021 12:43:00 Cindy Sue Causey wrote:
> > man lilo > manLILO
> did exactly what I wanted it to do. Thank you Cindy. ;o)
On Fri, Oct 01, 2021 at 05:07:37PM -0400, Gene Heskett wrote:
> On Friday 01 October 2021
On Friday 01 October 2021 13:58:20 Lee wrote:
> On 10/1/21, Gene Heskett wrote:
> > Greetings all;
> >
> > With the man markup subtracted, so what we save is exactly what we
> > see.
>
> Try the "--ascii" option - eg
> man --ascii man > /tmp/man.txt
>
> Regards,
> Lee
Cindy's suggestion worke
On Friday 01 October 2021 12:43:00 Cindy Sue Causey wrote:
> On 10/1/21, Gene Heskett wrote:
> > Greetings all;
> >
> > With the man markup subtracted, so what we save is exactly what we
> > see.
> >
> > Thanks.
> >
> > Cheers, Gene Heskett.
>
> Hi, Gene. I'm not sure if I'm understanding correct
On Fri, Oct 01, 2021 at 04:59:25PM -0400, Gene Heskett wrote:
> On Friday 01 October 2021 12:34:16 Larry Martell wrote:
>
> man -t /path/to/man/file >file.txt
> groff -mandoc /path/to/man/file > file.txt, both quadrupled the size with
> lots more markup.
>
> Not what I want obviously.
There is
On Friday 01 October 2021 12:34:16 Larry Martell wrote:
man -t /path/to/man/file >file.txt
groff -mandoc /path/to/man/file > file.txt, both quadrupled the size with
lots more markup.
Not what I want obviously.
Thanks Larry.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense
On Fri, Oct 01, 2021 at 12:24:50PM -0400, Gene Heskett wrote:
> With the man markup subtracted, so what we save is exactly what we see.
If you want to reproduce what you see when you type "man bash" (just as
an example), you would need to *retain* the "man markup", not subtract it.
So, right off t
There's tee that can be used just pipe the man page through it and into a
text file.
On Fri, 1 Oct 2021, Lee wrote:
> On 10/1/21, Gene Heskett wrote:
> > Greetings all;
> >
> > With the man markup subtracted, so what we save is exactly what we see.
>
> Try the "--ascii" option - eg
> man --as
On 10/1/21, Gene Heskett wrote:
> Greetings all;
>
> With the man markup subtracted, so what we save is exactly what we see.
Try the "--ascii" option - eg
man --ascii man > /tmp/man.txt
Regards,
Lee
On 10/1/21, Gene Heskett wrote:
> Greetings all;
>
> With the man markup subtracted, so what we save is exactly what we see.
>
> Thanks.
>
> Cheers, Gene Heskett.
Hi, Gene. I'm not sure if I'm understanding correctly, but.. I do this
(am using the LILO package as an example):
man lilo > manLILO
On Fri, Oct 1, 2021 at 12:25 PM Gene Heskett wrote:
>
> Greetings all;
>
> With the man markup subtracted, so what we save is exactly what we see.
Maybe one of these man option will work for you:
-t, --troff
Use groff -mandoc to format the manual page to stdout.
This option
Greetings all;
With the man markup subtracted, so what we save is exactly what we see.
Thanks.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the l
all of them.
>>
>> dhclient (8) - Dynamic Host Configuration Protocol Client
>> dhclient-script (8) - DHCP client network configuration script
>> dhclient.conf (5)- DHCP client configuration file
>> dhclient.leases (5) - DHCP client lease database
>
> Plus
st Configuration Protocol Client
> dhclient-script (8) - DHCP client network configuration script
> dhclient.conf (5)- DHCP client configuration file
> dhclient.leases (5) - DHCP client lease database
Plus the dhclient(8) manpage lists other related manuals in its SEE ALSO
section:
SEE
On Tue, 26 Sep 2017, Greg Wooledge wrote:
> For years, I have been searching back and forth and up and down in
> dhclient(8) and dhclient.conf(5) and finding NOTHING.
> Turns out the REASON I couldn't find anything was because some bright
> spark decided to split the documentation into multiple ma
Hey all,
I don't think I've ever seen this before, which doesn't necessarily
mean something, but still -- I can't seem to find something relevant
with Google either (except for the source of zsoelim, containing the
error message itself :-/), so I'm a tad worried.
I first noticed "man pkg-config"
ges, the ten longest are:
Rank Pages
-
1 1118 ethereal-filter(4)
2 335
3 214perltoc
4 160
5 151smb.conf
6 148arm-palmos-gcc
7 131
8 118
9 101
10 81 bash
Note: Because of the way I computed totals, I have
Hello Users of Debian,
I spent several weeks visiting and revisiting the issue of how to configure my
laptop's network setup and have noticed that something always seemed to be
missing. What I discovered finally was that indeed something has been: on
stable (Woody) the manpage for the
On Wed, Jan 15, 2003 at 01:17:34AM +0100, martin f krafft wrote:
> how do you convert a perldoc document into a manpage?
Use pod2man.
Cheers,
--
Colin Watson [[EMAIL PROTECTED]]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "uns
how do you convert a perldoc document into a manpage?
--
Please do not CC me! Mutt (www.mutt.org) can handle this automatically.
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' :proud Debian developer, admin, and user
`. `'`
`- Debian - when you hav
On Wed, Jun 27, 2001 at 09:51:03AM +0800, Eric Boo wrote:
> How do I at least get page up to work when I'm viewing man pages? Right now
> all
> I get are beeps when I try the page-up and page-down keys.
I have:
$ ls -l /etc/alternatives/pager
lrwxrwxrwx1 root root 13 Jun 27 21:4
Okay, I got it, sorry for the double post. Something screwed up.
--
Eric Boo
Wednesday, June 27, 2001, 10:08 AM
5 hours and 39 minutes
http://magicman.freeshell.org
Hi,
This message was resent because it didn;t seem to appear on the list.
How do I at least get page up to work when I'm viewing man pages? Right now all
I get are beeps when I try the page-up and page-down keys.
Page-down isn't so important as I can use the spacebar instead.
Neither do the up
In article <[EMAIL PROTECTED]>,
Sven Burgener <[EMAIL PROTECTED]> wrote:
>How do I properly print out the contents of a manpage?
The printer should have no problems with manpages. And if you use
'man -t blabla' you even get nice postscript output.
>When I do ":
On Sat, Sep 09, 2000 at 06:15:25PM -0700, kmself@ix.netcom.com wrote:
> You might also try:
>
> $ man foo | col -b
>
> ...to output straight ascii.
Thanks, that's simple and nice.
Regards
Sven
--
The UNIX Guru's view of sex:
unzip ; strip ; touch ; finger
mount ; fsck ; more ; yes ; umount
On Sat, Sep 09, 2000 at 10:12:40PM +0200, Sven Burgener ([EMAIL PROTECTED])
wrote:
> On Sat, Sep 09, 2000 at 09:59:55PM +0200, Christoph Groth wrote:
> > Sven Burgener <[EMAIL PROTECTED]> writes:
> > > How do I properly print out the contents of a manpage?
> > >
On Sat, Sep 09, 2000 at 11:41:32PM +0100, Glyn Millington wrote:
> OK. The trick is to get "man" to output in PostScript format:
> man -t will do it.
>
> Then use the utility "psnup" (one of the GNU pstools package.).
> It will print two or more pages of the man output onto one page,
> thus savi
On Sat, Sep 09, 2000 at 09:59:55PM +0200, Christoph Groth wrote:
> Sven Burgener <[EMAIL PROTECTED]> writes:
>
> > How do I properly print out the contents of a manpage?
> > When I do ":r! man blabla" in vi, I get funny characters at some places.
> >
&g
On Sat, Sep 09, 2000 at 10:12:40PM +0200, thus spake Sven Burgener:
> On Sat, Sep 09, 2000 at 09:59:55PM +0200, Christoph Groth wrote:
> > Sven Burgener <[EMAIL PROTECTED]> writes:
> > > How do I properly print out the contents of a manpage?
> > > When I do &q
Oh haha, the parameter is actually called "-m" ("macro"), the "an" is an
argument to the parameter. -chris
> That seems to do a fine job. I cannot find a documentation of that
> "-man" parameter anywhere. Where would that be? (checked the man
> page of *roff)
>
On Sat, Sep 09, 2000 at 01:29:32PM -0700, Krzys Majewski wrote:
> Sven Burgener <[EMAIL PROTECTED]> writes:
>
> > > Another way would be to directly use troff/nroff.
> >
> > Which is how? Never done this so please help me out a little.
>
> Well you can do something like this:
>
> 13:27:57$ zcat
Sven Burgener <[EMAIL PROTECTED]> writes:
> > Another way would be to directly use troff/nroff.
>
> Which is how? Never done this so please help me out a little.
Well you can do something like this:
13:27:57$ zcat man.1.gz | nroff -man > ~/tmp/woo
but this still puts funky characters in the ou
On Sat, Sep 09, 2000 at 09:59:55PM +0200, Christoph Groth wrote:
> Sven Burgener <[EMAIL PROTECTED]> writes:
> > How do I properly print out the contents of a manpage?
> > When I do ":r! man blabla" in vi, I get funny characters at some places.
> > Using man
Sven Burgener <[EMAIL PROTECTED]> writes:
> How do I properly print out the contents of a manpage?
> When I do ":r! man blabla" in vi, I get funny characters at some places.
>
> Using man's --ascii option didn't help.
You can use Emacs (Even if this is h
links.
** Now I have a question: **
How do I properly print out the contents of a manpage?
When I do ":r! man blabla" in vi, I get funny characters at some places.
Using man's --ascii option didn't help.
Sven
--
I can't be wrong, my modem's got error-correction.
Dear Scurvy Newbie
This is obviously a date problem. Run mandb -c man directories to
index all manpage and in the future make sure newly intalled manpage
date are later then the indexes or better yet go back to dos an never
darken this discussion group again you hapless scoundrel.
On
in slink its in nfs-server ..
if you need it you could prob grab it from there ..
nate
On Sun, 9 Jan 2000, Joseph Heenan wrote:
joseph >None of my systems (all running unstable) have a man page for
joseph >/etc/exports - am I missing a package somewhere, or is this a bug? I
joseph >expected it
None of my systems (all running unstable) have a man page for
/etc/exports - am I missing a package somewhere, or is this a bug? I
expected it to be in nfs-server or nfs-common, both of which I have
installed, and there's no sign of it in either.
bfn,
Joseph
--
Joseph Heenan, Coventry, UK
here is no
default man directory search to determine if that man page exists. I set
the $MANPATH but it makes no difference. Other man pages are called up with
"man command", if that manpage has never been called by man a file is
created in th
*- On 31 Dec, David Karlin wrote about "apt manpage missing"
> Hello,
> The manpage for apt seems to be missing, although the manpage for
> apt-get is present, on my (slink) system.
>
> I'd thought that a program's manpage is installed with the package
&g
Hello,
The manpage for apt seems to be missing, although the manpage for
apt-get is present, on my (slink) system.
I'd thought that a program's manpage is installed with the package
itself, but it doesn't seem to have happened in this case.
How can I get this manpage installed on
Hi everyone.
I'm going to file a bug report about this, but I thought I'd try and
gather a little more information first.
I'm running potato, and I just noticed there is no manpage for the
/etc/hosts file. I don't remember if there was one for slink (could
someone please let
Subject: Manpage
Date: Sat, 26 Sep 1998 12:15:48 PDT
From: "Gregory Walther" <[EMAIL PROTECTED]>
Sorry to bother everyone with such a simple question. Or maybe it's not
so simple, I don't know.
I installed debian 2.0 and I cannot get the "man&q
*-"Gregory Walther" <[EMAIL PROTECTED]>
|
| I installed debian 2.0 and I cannot get the "man" pages to work.
Hm, can you be more specific? Have you installed the packages
man-db and manpages?
You can check with 'dpkg -s ' (sustitute
man-db and manpages for ).
| I asked this same question somewh
>> "GW" == Gregory Walther <[EMAIL PROTECTED]> writes:
GW> I installed debian 2.0 and I cannot get the "man" pages to work.
You have to install the man-db package. This packages provides the man
command. Also install the manpages package.
Ciao,
Martin
> start.
>
> I asked this same question somewhere else last week. The response I got
> made me more confused. The respondent said use "groff." OK, what is it
> and how do I use it.
>
> I noticed on one web site that the lack of manpage setup on installation
> i
manpages would be a very good place to
start.
I asked this same question somewhere else last week. The response I got
made me more confused. The respondent said use "groff." OK, what is it
and how do I use it.
I noticed on one web site that the lack of manpage setup on installation
On 7 Aug, [EMAIL PROTECTED] wrote:
>
> Do I have to upgrade man page index somehow?
> Lesson learned: Debian is always right. Read man page carefully :)
>
You could try mandb, although I never called it mayself and never had
problems when I installed manpages to /usr/local.
Ciao,
Martin
page carefully :)
(*) especially to Dimitri (Dima), Martin.Bialasinski and Oliver Elphick (thanks
for manpage)
--
|||| ||| Marco Frattola Microsoft is not the answer
||`..'|| |||... Piacenza, ItalyMicrosoft is the question
||| ||| |||''
sing.
> Is this a (debian/linux) bug? Should I file a bugreport? Is there anybody who
> can send me that manpage?
>
dpkg -L xinetd shows:
[...]
/usr/man
/usr/man/man1
/usr/man/man1/xinetd.1.gz
/usr/man/man5
/usr/man/man5/xinetd.log.5.gz
/usr/man/man5/xinetd.conf.5.gz
[...]
This is xin
? Is there anybody who
can send me that manpage?
Thanks in advance
--
|||| ||| Marco Frattola Microsoft is not the answer
||`..'|| |||... Piacenza, ItalyMicrosoft is the question
||| ||| |||''[EMAIL PROTECTED]&qu
I think the last time we discussed this on the mailing lists, we
decided that there was no problem with compressed man page source.
The decompressor runs quickly, the man browsers all understand .gz
files, etc. I think that it's OK for packages to start installing
compressed man pages.
Bru
Derek Lee <[EMAIL PROTECTED]> writes:
> is there some way ask the install scripts to do so? I cannot just go
This issue has been discussed, but not resolved. It was decided to
wait until after the 1.1 release to deal with it. For now you would
probably be better off to try and just live with th
Hi,
I notice that the debian packages install man pages without
compression. If I would like to gzip all my man pages to save space,
is there some way ask the install scripts to do so? I cannot just go
in and gzip all the files in my /usr/man directories because:
(1) If all my man pages have .gz
94 matches
Mail list logo
