Complete.Org: Mailing Lists: Archives: gopher: August 2002:
[gopher] remove

[gopher] remove

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: <gopher@xxxxxxxxxxxx>
Subject: [gopher] remove
From: "Adam Kling" <adam@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 7 Aug 2002 11:51:12 -0400
Reply-to: gopher@xxxxxxxxxxxx

Adam Kling  (adam@xxxxxxxxxxxxxxxx)
CEO, E-Biz Hosting Solutions LLC - EXCELLENT small business web hosting - Premier JAVA hosting using the latest
technology! - Automate your sales and marketing! - Automate your Marketing!!!
Phone: 877-877-EBIZ(3249) X65
Fax: 877-877-3249
ICQ: 48465297

-----Original Message-----
From: gopher-bounce@xxxxxxxxxxxx [mailto:gopher-bounce@xxxxxxxxxxxx] On
Behalf Of John Goerzen
Sent: Wednesday, August 07, 2002 3:02 AM
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Process question

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
> 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
UMN.UMNDirHandler is enabled (it is by default) in your pygopherd.conf.

Regular UMN gopherd does not support adding .abstract files to the menu
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
techniques.  See the gophermap.BuckGophermapHandler option in

-- John

John Goerzen <jgoerzen@xxxxxxxxxxxx>    GPG: 0x8A1D9A1F

[Prev in Thread] Current Thread [Next in Thread]