Date: Wed, 7 Aug 2002 02:01:43 -0500
From: John Goerzen <jgoerzen@complete.org>
To: gopher@complete.org
Subject: [gopher] Re: Process question
Message-ID: <20020807070143.GB832@complete.org>
References: <20020806135709.A6583@pongonova.net>
 <3D50C2CC.50007@myrealbox.com>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3D50C2CC.50007@myrealbox.com>
User-Agent: Mutt/1.4i
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


On Wed, Aug 07, 2002 at 01:48:44AM -0500, Aaron J. Angel wrote:

> Yes, that's correct; if you use gophermap in directories, you have to
> add everything you want to be seen on the menu.  An alternative, if you
> just want a description for files, is to use metafiles (by creating a
> file with the same name and appending .abstract) to hold the
> descriptions.  This will still show anything that doesn't have an

Just a quick addendum -- Aaron's comments are assuming you are running
pygopherd.  Also, if you do use these options, you will need to make sure
UMN.UMNDirHandler is enabled (it is by default) in your pygopherd.conf.

Regular UMN gopherd does not support adding .abstract files to the menu in
this way, and in fact, the process of describing menu entries in the way
Aaron mentioned for PyGopherd will be very difficult with UMN gopherd.

It is true that gophermap is an all-or-nothing approach, and that if you
have a gophermap for a given directory, you will not be able to use these
techniques.  See the gophermap.BuckGophermapHandler option in
pygopherd.conf.

-- John

-- 
John Goerzen <jgoerzen@complete.org>    GPG: 0x8A1D9A1F    www.complete.org