Content-type: text/plain; charset=iso-8859-1
From: Timm Murray <hardburn@runbox.com>
To: gopher@complete.org
Subject: [gopher] Re: Gopher command line client
Date: Fri, 28 Jun 2002 16:10:09 -0500
References: <5.1.0.14.1.20020628213944.009f31d0@um1b.pce.de>
In-Reply-To: <5.1.0.14.1.20020628213944.009f31d0@um1b.pce.de>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200206281610.12653.hardburn@runbox.com>
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 28 June 2002 14:41, Wolfgang Zekoll wrote:
> Hello,
>
> I've a quick question.  Did someone of us ever think about programming
> a gopher client as a collection of UNIX shell commands?

 . . . And they will call it "netcat" or perhaps "telnet".

Seriously, for anything less than lynx or the UMN client, you might as well be 
using telnet.

- -- 
Real computer scientists don't program in assembler.  They don't write 
in anything less portable than a number two pencil.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj0c0LMACgkQqpueKcacfLTDEgCfevR6gKyguVYsk9YW42ctzr1r
3WMAn1P4gSejLNONiaceD1qHQ7KcQeGO
=VdvG
-----END PGP SIGNATURE-----