From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <5d375e920802111559kb5557d2k182a810ad4c11123@mail.gmail.com>
Date: Tue, 12 Feb 2008 00:59:17 +0100
From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] How to move to rc from sh/bash
In-Reply-To: <20080210181244.GA801@shodan.homeunix.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <b954b2060802082353h694ee9a3kd008351835d9f27a@mail.gmail.com>
	<599f06db0802100859l2a13a8e7o9d6a492138d44421@mail.gmail.com>
	<41F23396-1019-4C8E-A65A-E42824B0E23B@mac.com>
	<20080210181244.GA801@shodan.homeunix.net>
Topicbox-Message-UUID: 506e0a06-ead3-11e9-9d60-3106f5b1d025

> But what's really great about rc:
> % man bash | wc -l
>     4898
> % man rc | wc -l
>      398
> If I'd want to check the bash man page for some specific information,
> chances are that I'm sound asleep before anything interesting comes up.

It is more likely that the information you want is not even in the man
page, gnu man pages are severely crippled, and if you want the real
documentation you have to travel to info hell which is likely to
contain ten times as much (mis)information and be ten times harder to
browse.

And there you have the greatest innovation GNU has ever brought to
unix, in gnu systems I rarely even bother checking the docs, because
even random trial and error usually takes much less effort than
navigating the fetid info swamp.

uriel