Date: Sun, 13 Nov 2005 06:26:22 -0600
From: Benn Newman <newmanbe@sdf.lonestar.org>
To: gopher@complete.org
Subject: [gopher] Re: Gopher for dummies
Message-ID: <20051113122622.GA26367@SDF.LONESTAR.ORG>
References: <43761C9A.2000909@versateladsl.be>
 <20051112181841.GA2411@freeshell.org> <43771901.4000903@versateladsl.be>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43771901.4000903@versateladsl.be>
User-Agent: Mutt/1.4.2.1i
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

On Sun, Nov 13, 2005 at 11:44:17AM +0100, Walter Vermeir wrote:
> But the practical examples are very limited.  The best way to see how
> thinks works it to look at the source.  It would be very interesting if
> I could get the source files of a decent gopher site like
> 
> gopher://gopher.floodgap.com:70/1/
> 
> Greetings,
> Walter Vermeir
I'm fairly sure that the source (really the only version because it is
written in Perl) for bucktooth has it as an example.
<gopher://gopher.floodgap.com/1/buck>

Also try gopher://gopher.floodgap.com/0gophermap
-- 
Benn Newman
newmanbe@sdf.lonestar.org | gopher://igneous-rock.homeunix.net

Bradley's Bromide:                                                              
        If computers get too powerful, we can organize them into a              
committee -- that will do them in.