Received: with ECARTIS (v1.0.0; list gopher); Wed, 17 Apr 2002 11:20:48 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from pluto2.runbox.com (pluto2.runbox.com [193.71.199.74]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 793763B814 for ; Wed, 17 Apr 2002 11:20:37 -0500 (EST) Received: from mail by pluto2.runbox.com with local (Exim 3.33 #1) id 16xs9T-0001MT-00 for gopher@complete.org; Wed, 17 Apr 2002 18:19:23 +0200 Content-type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: "Timm Murray" To: gopher@complete.org Subject: [gopher] Re: Width of text files Date: Wed, 17 Apr 2002 16:19:23 GMT X-Sender: 79977 X-Mailer: RMM Message-Id: X-archive-position: 596 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: hardburn@runbox.com Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-ID: Gopher X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher <> > I still have to learn stuff about .names and other 'modification files',= =20 > since I only know how to set up .links files, but I'll take my time :) > The question is: how wide should I make the text files available via=20 > gopher? 80 columns? 80 col is the standard size for a console, so that should probably be the l= ine length for text files. It should also be possible to modify servers to = automatically adjust line lengths.