Date:	Sun, 9 Feb 2003 16:22:04 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp AT delorie DOT com
Subject:	Re: GCC warning - incompatible pointer type
In-Reply-To:	<3E460945.7FFD8D76@yahoo.com>
Message-ID:	<Pine.SUN.3.91.1030209161909.1383A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 9 Feb 2003, CBFalconer wrote:

> > But I urge you to invest a little more time in learning Info,
> > since it will let you find things much more efficiently.  For
> > starters, read the section about Info in the README.1ST file. 
> > HTML format doesn't give you the index search or the
> > TAB-completion on available topics, two of the more important
> > features of Info.
> 
> It certainly grows on you.

Sorry, I don't understand what did you mean by that.

> The principle nuisance (in info) is
> the absence of any means of printing out a node, or a collection
> of nodes.

That's not true: type "Alt-x print-node", hit [Enter], and there you go.

GUI Info readers have their own means to print a node.

You can also print a series of nodes by redirecting info.exe's output to 
the printer; see "info --help" for more.

> Here the HTML versions are very handy, as they will
> adapt directly to the page size used on the printer.  They have
> the distinct disadvantage of requiring mouse use to navigate, but
> are fine for continuous reading.

Most (if not all) users never read a manual in its entirety.  They only 
look in a manual for a specific topic or subject they need to know at 
that time.  That's where Info readers shine.

- Raw text -