this yet, not filled a bugreport to all of their
packages...
)
On 15.03.07 09:19, Carl Johnson wrote:
You should look at the dhelp and dwww packages and see if you like
either of them (I prefer dwww). They both provide browser access to
the man pages, info files, and the /usr/share/doc
On 14.03.07 08:35, Mike McClain wrote:
In man pages written by the FSF I see this advisory:
SEE ALSO
The full documentation for sync is maintained as a Texinfo manual. If
the info and sync programs are properly installed at your site, the
command
info
a bugreport to all of their
packages...
)
You should look at the dhelp and dwww packages and see if you like
either of them (I prefer dwww). They both provide browser access to
the man pages, info files, and the /usr/share/doc/* documentation.
--
Carl Johnson[EMAIL PROTECTED
In man pages written by the FSF I see this advisory:
SEE ALSO
The full documentation for sync is maintained as a Texinfo manual. If
the info and sync programs are properly installed at your site, the
command
info coreutils sync
should give you access to
in the info pages. I think that it is because
the FSF and GNU have a preference for info over man.
Regards,
-Roberto
--
Roberto C. Sanchez
http://people.connexer.com/~roberto
http://www.connexer.com
signature.asc
Description: Digital signature
Mike McClain writes:
In man pages written by the FSF I see this advisory:
SEE ALSO
The full documentation for sync is maintained as a Texinfo manual. If
the info and sync programs are properly installed at your site, the
command
info coreutils sync
On 3/14/07, Jhair Tocancipa Triana [EMAIL PROTECTED] wrote:
Mike McClain writes:
Has anyone seen am example where there was any more information in the info
pages than the man pages?
Yes, emacs.
And gmake, and autoconf, and ...
--
Michael A. Marsh
http://www.umiacs.umd.edu/~mmarsh
(or whichever one corresponds to your version, like gcc4.1-doc) then you
get the complete manual in the info pages. I think that it is because
the FSF and GNU have a preference for info over man.
From: Jhair Tocancipa Triana [EMAIL PROTECTED]
Yes, emacs.
From: Michael Marsh [EMAIL PROTECTED
-Servers kopieren. Und mal
Das habe ich gemacht und es funktioniert...
Danach kanste ein dwww-build laufen lassen und
er knallt Dir ein Extra-Verzeichnis mit HTML's voll...
Jetzt geht es eigentlich nur noch darum, wie ich alle
/usr/doc, /usr/info und /usr/man aus den Paketen meines
linuxnfs
Am 22:49 07/08/02 +0200 hat Rainer Ellinger geschrieben:
Michelle Konzack schrieb:
extrahieren und auf einen seperaten Server (doc.michelle.de)
Ist irgendwie schieef gegangen...
Stimmt. Ich finde da nur unter www. Deine Freundinnen =8-0 (scnr)
Ich weis zwar nicht WAS du gefunden hast, aber
On Sun, Jun 23, 2002 at 03:04:42AM +0100, Colin Watson wrote:
On Sat, Jun 22, 2002 at 02:45:39PM -0500, John Hasler wrote:
Osamu Aoki writes:
Another one is information on libc. apropos libc does not offer good
pointer to libc in manual page.
File a bug.
On what? Do you mean that
Good discussion! Learned something!
Thanks,
Paul
--
* For God so loved the world that He gave his only begotten Son, *
* that whoever believes in Him should not perish...John 3:16 *
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
When I see people who claim to like info, I really do wonder whether
they're talking about the same program.
There is info the documentation format and there is info the
standalone info browser and we both know they are different. I am
fine with the format and also fine with the browser,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jun 21, 2002 at 10:18:41PM -0500, John Hasler wrote:
which you can't get rid of (as far as I know).
^X-1 works for me. ESC-^f brings them back.
I wonder if whatever the author of info was on is legal when he thought
up those key
On Fri, Jun 21, 2002 at 10:18:41PM -0500, John Hasler wrote:
- When a page has a footnote, info feels a need to put it in a window
that fills half the screen, which you can't get rid of (as far as I
know).
I get a window just large enough for the footnote.
Yes, but when a footnote is
On Thu, Jun 20, 2002 at 07:15:32PM -0700, Paul Johnson wrote:
On Thu, Jun 20, 2002 at 10:02:43AM -0500, W. Paul Mills wrote:
Seems like I never can find what I want in info. Man pages are
much easier. Then again a friendlier info browser might help.
I mostly only hate info. Mostly
On Fri, Jun 21, 2002 at 10:18:41PM -0500, John Hasler wrote:
Peter De Wachter writes:
- There doesn't seem to be any way to scroll line-by-line or two lines at
a time (like lynx with Insert/Delete)
True.
False.
M-x set-variable scroll-step 1
I just discovered this in the info manual,
Hi,
at, Jun 22, 2002 at 04:56:52PM +0200, Peter De Wachter wrote:
On Fri, Jun 21, 2002 at 10:18:41PM -0500, John Hasler wrote:
Peter De Wachter writes:
- There doesn't seem to be any way to scroll line-by-line or two lines at
a time (like lynx with Insert/Delete)
True.
False.
On Sat, Jun 22, 2002 at 12:19:16PM -0700, Osamu Aoki wrote:
Another one is information on libc. apropos libc does not offer
good pointer to libc in manual page. info libc gives no clue.
It is info Libc. Why capitalize this?? I have no clue.
info libc works fine here... (sid). I
Osamu Aoki writes:
Another one is information on libc. apropos libc does not offer good
pointer to libc in manual page.
File a bug.
info libc gives no clue. It is info Libc. Why capitalize this?? I
have no clue.
Both 'info Libc' and 'info libc' work for me.
--
John Hasler
[EMAIL
On Sat, Jun 22, 2002 at 12:43:06PM -0700, Eric G. Miller wrote:
On Sat, Jun 22, 2002 at 12:19:16PM -0700, Osamu Aoki wrote:
Another one is information on libc. apropos libc does not offer
good pointer to libc in manual page. info libc gives no clue.
It is info Libc. Why capitalize
On Fri, Jun 21, 2002 at 10:18:41PM -0500, John Hasler quoted
Peter De Wachter who wrote:
I just discovered this in the info manual, which is BTW not 'info
info', but 'info info-stnd'. ('info info' gives only documents a small
portion of the keystrokes. I have a feeling it's
On Sat, 22 Jun 2002 07:40:26 -0700, Osamu Aoki wrote:
On Thu, Jun 20, 2002 at 07:15:32PM -0700, Paul Johnson wrote:
On Thu, Jun 20, 2002 at 10:02:43AM -0500, W. Paul Mills wrote:
snip
I mostly only hate info. Mostly. The only real way that I could find
to make info usable was info2html, and
Paul Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 20, 2002 at 10:02:43AM -0500, W. Paul Mills wrote:
Seems like I never can find what I want in info. Man pages are
much easier. Then again a friendlier info browser might help.
I mostly only hate info
On Sat, Jun 22, 2002 at 02:45:39PM -0500, John Hasler wrote:
Osamu Aoki writes:
Another one is information on libc. apropos libc does not offer good
pointer to libc in manual page.
File a bug.
On what? Do you mean that there should be some kind of summary man page
for libc pointing to
I wrote:
File a bug.
Colin Watson writes:
On what? Do you mean that there should be some kind of summary man page
for libc pointing to more useful sources of information?
Seems like that would answer Osamu's complaint. It could usefully mention
both the info file and the function man pages.
on Thu, Jun 20, 2002, W. Paul Mills ([EMAIL PROTECTED]) wrote:
[EMAIL PROTECTED] (Colin Watson) writes:
Seems like I never can find what I want in info. Man pages are
much easier. Then again a friendlier info browser might help.
No, scrap the whole format. DocBook w/ mandetory manpages would
On Thu, 20 Jun 2002 20:05:37 BST, Colin Watson writes:
On Thu, Jun 20, 2002 at 05:36:58PM +0100, Colin Watson wrote:
On Thu, Jun 20, 2002 at 05:33:42PM +0200, Robert Waldner wrote:
But http://freshmeat.net/projects/info2man/ helps.
(no .deb available though, AFAICT)
That's *very* nice.
authors and readers can pick up
quickly. I'm in the habit of using info for a very few GNU packages
(make, autoconf, and the libc being prime examples), but given the
choice I still prefer a quick 'man foo'.
Seems like I never can find what I want in info. Man pages are
much easier. Then again
to more authoritative
documentation, so I can recall the programs interface. When I want to
research the program, I will always hope there would be info or a
postscript document, not a man page. Both man and info are very useful.
It would be a pity to see projects try to side with one or the other
Hi Karsten,
On Fri, Jun 21, 2002 at 12:32:22AM -0700, Karsten M. Self wrote:
on Thu, Jun 20, 2002, W. Paul Mills ([EMAIL PROTECTED]) wrote:
[EMAIL PROTECTED] (Colin Watson) writes:
Seems like I never can find what I want in info. Man pages are
much easier. Then again a friendlier info
Info isn't intuitive enough to be of practical value. You can't quickly
sit down, search for what you need, and then go on. You have to
memorize a bunch of key strokes that are easily forgotten. I only use
info if I'm desperate.
I really like info because it is very quick to start up,
Bob writes:
Are we talking about the same documentation format?
I wonder that myself whenever I see someone bashing info.
--
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wisconsin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
feels a need to put it in a window
that fills half the screen, which you can't get rid of (as far as I
know).
Maybe these things are answered in the documentation, but 'info info'
gives documentation on another program, 'man info' only lists the
command line options, and /usr/share/doc/info
Peter De Wachter writes:
- There doesn't seem to be any way to scroll line-by-line or two lines at
a time (like lynx with Insert/Delete)
True.
- There doesn't seem to be any way to search on regexps
True.
- When a page has a footnote, info feels a need to put it in a window
that fills
info for a very few GNU packages (make,
autoconf, and the libc being prime examples), but given the choice I
still prefer a quick 'man foo'.
Seems like I never can find what I want in info. Man pages are
much easier. Then again a friendlier info browser might help.
Paul
--
* For God so
On Thu, 20 Jun 2002 10:02:43 CDT, W. Paul Mills writes:
Seems like I never can find what I want in info. Man pages are
much easier. Then again a friendlier info browser might help.
AOL!
But http://freshmeat.net/projects/info2man/ helps.
(no .deb available though, AFAICT)
cheers,
rw
--
/ Ing
On Thu, Jun 20, 2002 at 10:02:43AM -0500, W. Paul Mills wrote:
[EMAIL PROTECTED] (Colin Watson) writes:
Man pages are things that both authors and readers can pick up quickly.
I'm in the habit of using info for a very few GNU packages (make,
autoconf, and the libc being prime examples), but
[EMAIL PROTECTED] (W. Paul Mills) writes:
Seems like I never can find what I want in info. Man pages are
much easier. Then again a friendlier info browser might help.
Do you know about the s and i keys? They let you search the whole
file or search the index, respectively. That should make
Seems like I never can find what I want in info. Man pages are
much easier. Then again a friendlier info browser might help.
Paul
apt-get install pinfo
or if you have apache installed
apt-get install info2www
hope this helps
pietro.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
On Thu, Jun 20, 2002 at 05:33:42PM +0200, Robert Waldner wrote:
On Thu, 20 Jun 2002 10:02:43 CDT, W. Paul Mills writes:
Seems like I never can find what I want in info. Man pages are
much easier. Then again a friendlier info browser might help.
AOL!
But http://freshmeat.net/projects
On Thursday 20 June 2002 17:02, W. Paul Mills wrote:
Seems like I never can find what I want in info. Man pages are
much easier. Then again a friendlier info browser might help.
If you have a web server that can handle CGI scripts, you might want to
try the info2www package. I like
On 20 Jun 2002, Colin Watson wrote:
On Thu, Jun 20, 2002 at 10:02:43AM -0500, W. Paul Mills wrote:
[EMAIL PROTECTED] (Colin Watson) writes:
Man pages are things that both authors and readers can pick up quickly.
I'm in the habit of using info for a very few GNU packages (make,
On Thu, Jun 20, 2002 at 05:36:58PM +0100, Colin Watson wrote:
On Thu, Jun 20, 2002 at 05:33:42PM +0200, Robert Waldner wrote:
But http://freshmeat.net/projects/info2man/ helps.
(no .deb available though, AFAICT)
That's *very* nice. There might just be a .deb coming soon.
It's now in
authors and readers can pick up quickly.
I'm in the habit of using info for a very few GNU packages (make,
autoconf, and the libc being prime examples), but given the choice I
still prefer a quick 'man foo'.
Seems like I never can find what I want in info. Man pages are
much easier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 20, 2002 at 10:02:43AM -0500, W. Paul Mills wrote:
Seems like I never can find what I want in info. Man pages are
much easier. Then again a friendlier info browser might help.
I mostly only hate info. Mostly. The only real way that I
I much prefer 'man' to 'info' (and I guess at least some Debian developers
do too as there are so many Debian-edited man pages). Anyone know why GNU
uses info now instead? And is there any way to influence the decision, or
am I just way too late?
Patrick
--
Patrick Wiseman
[EMAIL PROTECTED
On Mon, Jun 17, 2002 at 05:49:28PM -0400, Patrick Wiseman wrote:
I much prefer 'man' to 'info' (and I guess at least some Debian developers
do too as there are so many Debian-edited man pages). Anyone know why GNU
uses info now instead? And is there any way to influence the decision, or
am I
On Mon, 17 Jun 2002, Simon Law wrote:
So you see, there is a place for both types of documentation.
Thanks for that very articulate and helpful description of the value of
each - and, yes, I do now see :)
Patrick
--
Patrick Wiseman
[EMAIL PROTECTED]
Linux user #17943
--
To
On Mon, Jun 17, 2002 at 05:49:28PM -0400, Patrick Wiseman wrote:
I much prefer 'man' to 'info' (and I guess at least some Debian developers
do too as there are so many Debian-edited man pages). Anyone know why GNU
uses info now instead? And is there any way to influence the decision, or
am I
BTW, an excellently written summary. Thanks Simon.
Note that the GNU project does not disapprove of man pages; it's just
that many of their maintainers are too busy to maintain both man and
info documentation.
Many GNU projects such as the GNU coreutils of fileutils, textutils,
sh-utils, etc
_somewhat_ work things out, if only by the man page section (man
man for info), which will tell you if the page is a command, a file,
system or library call, or other component. Could be better, but at
least it's there.
Peace.
--
Karsten M. Self kmself@ix.netcom.comhttp
on Wed, Dec 26, 2001 at 08:10:46PM -0500, dman ([EMAIL PROTECTED]) wrote:
On Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch wrote:
| ((X)Emacs is everywhere).
Hmm,
$ dpkg -l \*emacs\* | grep ^ii
$
I think I just found nowhere :-).
...but are you in the _middle_ of it. That's
On Wed, Dec 26, 2001 at 01:48:55PM -0800, Karsten M. Self wrote:
on Wed, Dec 26, 2001 at 02:29:19PM -0600, Colin Watson
([EMAIL PROTECTED]) wrote:
Ugh, yes, that's horrible formatting. '.nf' means no-fill mode, but it
has the effect you're thinking of. Make sure you add this line to the
On Tue, 25 Dec 2001 17:24:26 +0100, Imre Vida
[EMAIL PROTECTED] wrote:
As far as info is concerned, i fully agree with Karsten.
It doesn't work intuitively for me either; i just get
lost in the maze of links and 3 sentence pages
I hate it for this.
Use pinfo. Feels like lynx. Much more
On Tue, Dec 25, 2001 at 03:02:25PM -0800, Karsten M. Self wrote:
on Tue, Dec 25, 2001 at 12:51:09PM -0600, Colin Watson
([EMAIL PROTECTED]) wrote:
Come up with examples and send patches. That'll achieve results much
faster than anything else I can think of.
Specific instructions on how to
On Tue, Dec 25, 2001 at 02:26:56PM -0800, Karsten M. Self wrote:
on Tue, Dec 25, 2001 at 08:07:40AM -0600, Colin Watson
([EMAIL PROTECTED]) wrote:
No, usually what's happened in these cases is that the man page is in
the main package while the info pages are in a separate -doc package
Karsten M. Self wrote:
on Tue, Dec 25, 2001 at 06:32:31PM -0800, Craig Dickson ([EMAIL PROTECTED])
wrote:
Carl Fink wrote:
BTW, for HTML docs, put them all in *one* file with hyperlinks. There is
no
meaningful advantage to cutting it into twenty pieces, and it makes
on Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch ([EMAIL PROTECTED])
wrote:
Karsten M. Self wrote:
on Tue, Dec 25, 2001 at 06:32:31PM -0800, Craig Dickson ([EMAIL PROTECTED])
wrote:
Carl Fink wrote:
BTW, for HTML docs, put them all in *one* file with hyperlinks.
on Wed, Dec 26, 2001 at 03:38:20PM +, Colin Watson ([EMAIL PROTECTED])
wrote:
On Tue, Dec 25, 2001 at 03:02:25PM -0800, Karsten M. Self wrote:
on Tue, Dec 25, 2001 at 12:51:09PM -0600, Colin Watson
([EMAIL PROTECTED]) wrote:
Come up with examples and send patches. That'll achieve
Karsten M. Self writes:
My concern was whether or not I should post my revised manpage to the
bugtracking system itself.
You should.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
On Wed, Dec 26, 2001 at 10:59:58AM -0800, Karsten M. Self wrote:
on Wed, Dec 26, 2001 at 03:38:20PM +, Colin Watson
([EMAIL PROTECTED]) wrote:
Do use the bug tracking system. In the case of printcap(5), a bug
should be filed against the three packages that contain it (lpr,
lprng,
On Wed, Dec 26, 2001 at 10:52:33AM -0800, Karsten M. Self wrote:
on Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch
([EMAIL PROTECTED]) wrote:
I think a decent search facility is a must for more in-depth
documentation. If I _know_ that I want to use newwin(3), I can easily
type man
on Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch ([EMAIL PROTECTED])
wrote:
Karsten M. Self wrote:
...
This can be further mitigated by browsers that render on partial
load, or which allow background loading of pages (Galeon rocks for
this).
Sorry, I disagree. Try
info
on Wed, Dec 26, 2001 at 02:29:19PM -0600, Colin Watson ([EMAIL PROTECTED])
wrote:
On Wed, Dec 26, 2001 at 10:59:58AM -0800, Karsten M. Self wrote:
on Wed, Dec 26, 2001 at 03:38:20PM +, Colin Watson
([EMAIL PROTECTED]) wrote:
Do use the bug tracking system. In the case of printcap(5),
On Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch wrote:
| You might argue that I should use w3m or links to read those large HTML
| files - but then I would have to remember the keystrokes of these
| programs (i.e. I can't use my favourite browser) and I have to
| install/build these
Karsten M. Self wrote:
on Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch ([EMAIL PROTECTED])
wrote:
Karsten M. Self wrote:
This can be further mitigated by browsers that render on partial
load, or which allow background loading of pages (Galeon rocks for
this).
Sorry, I
On Thu, Dec 27, 2001 at 02:14:36AM +0100, Michael Mauch wrote:
| Galeon 1.0 from the Debian system really is a lot faster (2 seconds
| for the whole file). So maybe something went wrong with my
| Galeon-0.12.7 build here (built from sources on something that once
| was a SuSE-6.1).
Ok, so galeon
hi,
i just read the (sub)thread above on man v. info
and i thought it is much more important than
to have it hidden in there. So i thought i try
to pick it up again.
The major sources of help/information for me are
the apropos, the -h/--help options and the man pages.
These are fast
On Tue, Dec 25, 2001 at 05:24:26PM +0100, Imre Vida wrote:
The lack of manpages, and outdated manpages are frustrating.
And what Karsten brought up is also a nice idea:
to have examples in man pages. There are some manpages with examples
but most of them are without although they are really
Imre == Imre Vida [EMAIL PROTECTED] writes:
Imre As far as info is concerned, i fully agree with Karsten. It
Imre doesn't work intuitively for me either; i just get lost in
Imre the maze of links and 3 sentence pages I hate it for
Imre this.
It's not man versus info
on Tue, Dec 25, 2001 at 08:07:40AM -0600, Colin Watson ([EMAIL PROTECTED])
wrote:
On Tue, Dec 25, 2001 at 02:21:55AM -0800, Karsten M. Self wrote:
on Tue, Dec 25, 2001 at 03:54:36AM -0200, Christoph Simon ([EMAIL
PROTECTED]) wrote:
On Mon, 24 Dec 2001 20:38:49 -0800
Karsten M. Self
* Imre Vida ([EMAIL PROTECTED]) spake thusly:
hi,
i just read the (sub)thread above on man v. info
and i thought it is much more important than
to have it hidden in there. So i thought i try
to pick it up again.
The major sources of help/information for me are
the apropos, the -h
on Tue, Dec 25, 2001 at 12:51:09PM -0600, Colin Watson ([EMAIL PROTECTED])
wrote:
On Tue, Dec 25, 2001 at 05:24:26PM +0100, Imre Vida wrote:
The lack of manpages, and outdated manpages are frustrating.
And what Karsten brought up is also a nice idea:
to have examples in man pages. There
On 25-Dec-01 Imre Vida wrote:
[snip]
The major sources of help/information for me are
the apropos, the -h/--help options and the man pages.
These are fast and efficient means to find what i want
most of the time.
As far as info is concerned, i fully agree with Karsten.
It doesn't work
World, isn't it?
I despise info. Use man as a base, and anything more elaborate that
actually *requires* hyperlinking, use HTML.
BTW, for HTML docs, put them all in *one* file with hyperlinks. There is no
meaningful advantage to cutting it into twenty pieces, and it makes
searching significantly
Carl Fink wrote:
BTW, for HTML docs, put them all in *one* file with hyperlinks. There is no
meaningful advantage to cutting it into twenty pieces, and it makes
searching significantly more difficult.
For locally-stored docs that's arguable. The advantage of small files
comes when you have
on Tue, Dec 25, 2001 at 06:32:31PM -0800, Craig Dickson ([EMAIL PROTECTED])
wrote:
Carl Fink wrote:
BTW, for HTML docs, put them all in *one* file with hyperlinks. There is no
meaningful advantage to cutting it into twenty pieces, and it makes
searching significantly more difficult.
On Tue, 25 Dec 2001 [EMAIL PROTECTED] wrote:
I really agree with this. I find 'info' very frustrating;
[...]
As to what to do about it, I can only suggest
reinstate the man pages in full. I know it's
not 'kosher' to disagreee with the GNU info
policy, but I think that those who do disagree
On Sun, Sep 02, 2001 at 11:54:09PM -0400, Brian Nelson wrote:
I also agree. I think what bothers me most about info pages is that
they often read like books. They're usually arranged in a format
resembling chapters covering each topic in thorough detail. This is
fine if I want to read a
Brian Nelson wrote:
I also agree. I think what bothers me most about info pages is that
they often read like books.
Not suprising, they often *are* books. I have a book on my shelf that
has about a 100% correspondence to the gdb info page. Though the gdb
info page lacks RPM's autograph..
--
On Sun, Sep 02, 2001 at 03:13:10PM -0700, Karsten M. Self wrote:
on Sun, Sep 02, 2001 at 01:44:45PM +0200, Cliff Sarginson ([EMAIL PROTECTED])
wrote:
On Sun, Sep 02, 2001 at 11:49:11AM +0100, Colin Watson wrote:
On Sat, Sep 01, 2001 at 10:31:47PM +0800, Rino Mardo wrote:
regretful snip
I
wow. ever thought of getting into law practice? :-)
i think i touched on a very touchy issue here. i'll just go find a simple
project for my python.
thanks for all the replies guys!
_
Do You Yahoo!?
Get your free @yahoo.com address at
on Sun, Sep 02, 2001 at 01:44:45PM +0200, Cliff Sarginson ([EMAIL PROTECTED])
wrote:
On Sun, Sep 02, 2001 at 11:49:11AM +0100, Colin Watson wrote:
On Sat, Sep 01, 2001 at 10:31:47PM +0800, Rino Mardo wrote:
getting a little OT here but can all the man databases be converted to
info
On Sun, Sep 02, 2001 at 03:13:10PM -0700, Karsten M. Self wrote:
Personally, I'd strongly recommend that the GNU project revisit the
issue of info pages altogether. They're not popular, they don't
adequately replace man pages, and there is a far more successful and
ubiquitous hypertext model
Karsten M. Self kmself@ix.netcom.com writes:
The problem is that this is often specifically what is *not* sought by
those who are looking for manpages. What's wanted is a short, concise,
but illustrative reference providing:
- A functional description of the command.
- A synopsis of
86 matches
Mail list logo
