HDTenEightyP/NetNews huggingface dataset:
From: jml4@cus.cam.ac.uk (John Line)
Subject: queries: is there a line-mode UNIX client, & xgopher "hanging"
Organization: U of Cambridge, England
Date: Mon, 27 Jul 1992 21:48:29 GMT

I recently (last Friday) made the UNIX curses and X clients available to
Computing Service staff here for evaluation (as in, should we be promoting
use of gopher and maybe setting up a server; you can guess my views since I
set it up...).

Two queries result from feedback so far:

(1) If we were to provide anonymous client access, it would (probably, for
"political" reasons) have to give the option of "line-mode" working (no screen
addressing, input terminated by the RETURN key), since there are still a lot of
old terminals in use and their owners would be (rightly) upset at being
excluded from gopher access (especially if we were using it to provide our own
primary campus information service...). I've seen suggestions here in the past
that a line-mode client would be useful - but no responses saying "got one" or
"yes, we'll put it on the wish-list and do it sometime".

Is there any prospect of either the standard curses gopher client learning how
to cope with really dumb terminals, or a totally separate program providing
equivalent functionality?

(2) As stated to me (paraphrased) "Using xgopher, I started a search and it
didn't do anything for a very long time. I couldn't find any way to stop it
short of killing the process."

Is that true (I'd hit the problem before, but assumed there must be a way...),
and if so, is there any prospect of a "cancel" button to interrupt xgopher when
waiting for a connection or a search to complete or any other predictably
(sometimes-)time-consuming operation? (Version in use is xgopher 1.1, with
X11R4.)

                                John
-- 
John Line - Cambridge University Computing Service, Computer Laboratory,
            New Museums Site, Pembroke Street, Cambridge CB2 3QG, ENGLAND.
Internet: jml4@cus.cam.ac.uk  JANET: jml4@uk.ac.cam.cus  Phone: +44 223 334708
From: THOR@USDCSV.ACUSD.EDU (I don't know)
Newsgroups: alt.gopher
Subject: gindexd
Date: 28 Jul 92 18:01:44 GMT
Distribution: alt
Original-To: gopher-news@boombox.micro.umn.edu
X-Vmsmail-To: SMTP%"gopher-news@boombox.micro.umn.edu"

Hello,

  We are trying to set up the index server for the unix gopher 1.01 and we
are having some problems.  We got WAIS compiled and then tried the 
"make wais" described in the gindexd docs, but got this error.

Undefined:
log_file_name
logfile
command_name
sdir
cdir
Sources
NumSources
find_value
PrintStatus
*** Error code 1

   I have tried to find these definitions, but without any luck.  Any body
got any ideas?

   Any help would be appreciated.

   thor
From: bill@waikato.ac.nz
Newsgroups: alt.gopher
Subject: Re: WHOIS Gopher links
Date: 31 Jul 92 09:41:47 +1200
Organization: University of Waikato, Hamilton, New Zealand

Matt Power has updated his Whois gopher links file. It's available via
anonymous FTP in

   sipb.mit.edu:/pub/whois/whois-servers.gopher-links

Could whoever looks after the gopher FTP files at boombox.micro.umn.edu
please update the file

   /pub/gopher/incoming/whois.links

with the new version. Thanks.

Bill Teahan
University of Waikato,
Hamilton, New Zealand

"I have never been lost, but I will admit to being confused for several weeks."
-- Daniel Boone.
Newsgroups: alt.gopher
From: billy@sol.acs.unt.edu (Billy Barron - VAX/UNIX Systems Manager)
Subject: official g2nntp
Organization: University of North Texas
Date: Fri, 31 Jul 1992 13:26:00 GMT

I am aware of at least two different Gopher to NNTP programs.  I am running
the one from LSU and not the one from Stanford.  I think it would be preferable
to standardize on ONE if possible.  The LSU one is straight-forward and has
worked flawless for me.

Any opinions especially from U of Minn?


Newsgroups: alt.gopher
From: billy@sol.acs.unt.edu (Billy Barron - VAX/UNIX Systems Manager)
Subject: Re: index for all of gopherspace
Organization: University of North Texas
Date: Mon, 27 Jul 1992 18:05:09 GMT

daniel@nstn.ns.ca (Daniel MacKay) writes:

>Now, the WAIS thang works because all the people who run WAISs, have sent
>in to the mother of all WAISs, an abstract for each database they've
>published.  
>
Not all.  I've found quite a few WAISs that are NOT in the master directory.
This also is the biggest problem with WAIS.  The directory is flat and getting
too big.

>Here's the problem I'm trying to solve: I know somewhere in gopherspace
>there's a really good recipe database.  But where is it?
>
I agree this is a BIG problem.  I was going to bring it up at the Gopher
Developer's Conference in a couple of weeks and see what could be worked
out.

>You send a query to the meta-database server, and it returns a
>list of databases.  You pick one [or several- but we can't do this without
>overhauling the client] of those, and your client sends a search off to
>them.
>Now, why couldn't we do this with gopher?
>
This could be done.  Actually, I don't really care to make this a "user"
feature.  It would involve some major coding and maybe a protocol change.
Just something us sysadmins use to figure out where we would like to place
links to.
From: urle@rz.uni-karlsruhe.de (Uli Betzler (urle))
Subject: Gopher Type 6 ???
Organization: University of Karlsruhe, Germany
Date: Tue, 21 Jul 1992 10:38:39 GMT

In the bintype-patch (boombox.micro.umn.edu:/pub/gopher/incoming/bintypes.patch)
there is a new type 6 (*.uue) introduced ? Why this new type ?

If this is uuencoded text you could serve the file like it is done with
compressed text - uudecode the text and show it as type 0.
If it is a binary uuencoded file, treat it as binary.

Or did I miss anything ?

urle


-- 
Ulrich Betzler                             smtp:   urle@rz.uni-karlsruhe.de
Universitaet Karlsruhe                     bitnet: rz83 at DKAUNI2
Rechenzentrum
Zirkel 2                                   X.500:  cn=Ulrich Betzler
7500 Karlsruhe 1                                   ou=Rechenzentrum
FRG                                                o=Uni-Karlsruhe
                                                   c=DE
phone: +49 721 608-4039
From: brintle@tinyblue.cs.uiowa.edu (Lee Brintle)
Newsgroups: alt.gopher
Subject: Request: approval and support of read-only options
Date: 30 Jul 92 01:47:59 GMT
Reply-To: brintle@tinyblue.cs.uiowa.edu (Lee Brintle)
Organization: U of Iowa, Iowa City, IA, USA


We've been using a read-only extension to the Gopher protocol for about
six months at U Iowa.  Basically, the server can send back information
in a gopher menu that is for information about the menu only.

They have been a vital and useful part of our menuing system; it's much
nicer to see a few lines about what the menu is about rather than having
the user choose the first option ("About...") to see what is going on.

As an example of this idea in action, please telnet to panda.uiowa.edu
and look at some of the main screens.  They lend a great deal of clarity
to what is going on...

Graphical clients display read-only information in a "header" and a "footer"
window above and below the options.  Any text mixed in with other options is
simple non-selectable.  It works.  It's easy.

Currently, we use type "i" for this, but any letter will do.

Lee Brintle                      | ``And so, I leave you with this final word:
Project Panda                    |              twang.''
From: rww@mugwump.cl.msu.edu (Richard W. Wiggins)
Newsgroups: alt.gopher
Subject: Human factors in PC Gopher II
Keywords: PC Gopher II
Date: 22 Jul 92 04:31:11 GMT
Organization: Michigan State University


In watching a microlab full of folks use PC Gopher II more than once,
I seem to observe a pattern: People don't know understand the 
distinction between closing a text window that's opened up,
versus hopping back a menu level.  Thus invariably they type
Alt-F3 when they don't mean to.  This of course closes their current
Gopher session.

I'm not too familiar with Turbo Vision and its options, but would it
be possible to make the keystroke one types consistent for closing
a text window and for "hopping up" one level?  In my opinion the
Escape key would be a good choice.

/Rich Wiggins, Gopher Coordinator, Michigan State U
From: jqj@nntp.uoregon.edu (JQ Johnson)
Newsgroups: alt.gopher
Subject: Re: Whois/finger patch for Unix client
Date: 21 Jul 92 15:13:30 GMT
Organization: University of Oregon Network Services

Any new extension mechanism for gopher should do more than the present
"add a new type" mechanism.  I see the major current problem with the
protocol being an overloading of the semantics of the type character.
Currently, it is used to distinguish:
  -	different kinds of object on a server (e.g. different file
	content types)
  -	different network interaction protocols (e.g. menu based file
	retrieval, telnet, etc.)
  -	[if the Schemers approach is widely adopted] different
	argument parsing protocols i.e. different interpretations of
	the selector line
  -	etc.

I see these as largely orthogonal.  For example, I can imagine wanting
string RPC arguments [the RS protocol] for any 0-like or 1-like gopher
type, but I note that they are not very relevant to the telnet type.
I can imagine a different style of argument processing also being
desired, again applying to any type of returned object.  And so on.

Bottom line:  a protocol extension mechanism should satisfy new needs.
Unfortunately, I'm not convinced we know yet what those new needs are.

P.S.: we do have SOME ideas of the new needs.  It's clear that many
people want more attributes/properties available for file-like
objects, e.g. creator, who to contact, etc (the Brown proposal).
It's clear that a more powerful alternation mechanism than the present
"+" type is desirable to allow clients to select their preferred
representation of equivalent data.  It's clear that the present
single-character filetype space is too small.  It's clear we need to
continue to think about scripting and such.  It may be that some type
of authentication mechanism is needed.  And so on.  The real challenge
may be to build extensions that preserve protocol purity and simplicity.
-- 
JQ Johnson
Director of Network Services		Office: 250E Computing Center
Computing Center			Internet: jqj@ns.uoregon.edu
University of Oregon			voice:	(503) 346-1746
From: boone@convex.cl.msu.edu (Dennis Boone)
Newsgroups: alt.gopher
Subject: Re: Gopher Road Map tool "gophertree"
Keywords: tree listing road map gopher gophertree
Date: 22 Jul 92 19:10:20 GMT
Organization: Michigan State University, East Lansing

In article <1992Jul21.205327.13158@msuinfo.cl.msu.edu> boone@convex.cl.msu.edu (Dennis Boone) writes:
>This tool creates an indented listing of the files in a Gopher server.
>We feel that a listing like the one created by gophertree will be helpful
>to new users as they begin using Gopher.  Later, as they develop confidence,
>it becomes a useful index.  By default, the listing is set up for printing
>on standard letter paper, but the program is configurable.  A sample listing
>appears below.

A couple of notes that I probably should have included in the first place.

1. gophertree won't follow links off the machine where it started, to prevent
recursive behavior.

2. Matching of the hostname is essentially of the string-compare nature, so
you need to specify the complete domain name on the command line.

3. To start with the root directory, specify no path, for best results.

4. We intend to post the report in some convenient place in our hierarchy
as part of the production service.

Dennis Boone
Michigan State University
--
 == Frustration is portable. ==
Xref: sparky alt.gopher:1058 comp.windows.x.apps:609
From: tunxis@netcom.com (Gary A. Gorgen)
Newsgroups: alt.gopher,comp.windows.x.apps
Subject: Re: Problem compiling XGopher/Imake problem
Summary: Tabs in Makefiles
Keywords: xgopher imake xmkmf problem
Date: 23 Jul 92 14:54:24 GMT
Followup-To: poster
Organization: Tunxis Design Inc. (408-749-9463)


In article <1992Jul21.154252.13664@trentu.ca>, ccgwt@trentu.ca (Grant Totten) writes:
}|> Problem:
}|> 
}|> 	I ftp'd and untarred the xgopher-1.1 release (is this the most
}|> recent version?) and read the README file.  Then did an xmkmf.  No
}|> problems.  Then did a make depend and got:
}|> 
}|> Make: Must be a separator on rules line 266.  Stop.
}|> 

This type of problem is usually caused by leading "TABS" in a 
macro definition. "Make" doesn't like this. In the Makefile, 
check around close to the line with the error. 
Change the "TABS" to "spaces", or remove the white
space altogether.
Try to fix the Makefile first, to find out what the problem is.
After you find the problem, which is probably in one of the include
files Imake uses, you will have to fix that file.
If there are any ".cf, .tmpl, .rules" files, in the xgopher directory,
check them out also. If one of these has "TABS" in a macro definition,
it will migrate into the Makefile, each time you do an Imake.
The leading "TABS" can creep into files from text editors.

I have a text editor that insists on collapsing leading white space
into "TABS". I've become an Xspert :-) on:
	 Make: Must be a separator on rules line 266.  Stop.

Edit the Makefile only to find the problem! Go back to the include
files and fix it. If it is in one of the Xgopher distribution files,
notify the person responsible, so they can fix it.

}<1992Jul22.153713.21278@cbnewsi.cb.att.com>
}rhb@hotsand.cnet.att.com (Richard H. Brandwein +1 908 949 2135)
	Writes:

}I get my error on line 275:
}
}	make: Fatal error in reader: Makefile, line 275: Unexpected end of
}	line seen
}
}which has a "InstallNonExecFile(xgopher,help,$(XGOPHERDIR))"
}statement.

This is probably caused by a missing include file, or improperly defined
macro.


I hope this helps.
If not send mail of the ftp address, and path, of where I can find Xgopher
and I will look into it in more detail.

Gary.



-- 
Gary A. Gorgen      | "From ideas to PRODUCTS"
tunxis@netcom.com   | Tunxis Design Inc.
                    | 422 S. Murphy, Sunnyvale Ca. (408) 749-9463
Newsgroups: alt.gopher
From: pbh@athena.mit.edu (Paul B Hill)
Subject: Is there a gopher for LAN WorkPlace for DOS?
Organization: Massachusetts Institute of Technology
Date: Wed, 29 Jul 1992 20:22:54 GMT

Does anyone know if there is a gopher client available that is compatible with
Novell's LAN WorkPlace for DOS, Novell's TCP/IP client package ?
Newsgroups: alt.gopher
From: michele@apex.yorku.ca (Michele Marques)
Subject: Mac Server question
Organization: York University, Help Services, CCS
Date: Wed, 22 Jul 1992 03:32:14 GMT


How do I put a title on my root directory?  Currently it just
says "Root Gopher Server" and where it is.

		-- Michele

Michele Marques                      | UUCP: ....!utzoo!yunexus!michele
Computing Help Desk                  | Internet: michele@apex.ccs.yorku.ca
Computing & Communications Services  | Bitnet:   michele@yuorion
York University                      | Voice:    +1-416-736-5800
--
Michele Marques                      | UUCP: ....!utzoo!yunexus!michele
Computing Help Desk                  | Internet: michele@apex.ccs.yorku.ca
Computing & Communications Services  | Bitnet:   michele@yuorion
York University                      | Voice:    +1-416-736-5800
Date: 22 Jul 1992 12:44:27 -0700
From: Brad_Stone@byu.edu
Subject: Gopher and Hypertext links
Original-To: gopher-news@boombox.micro.umn.edu
Content-Transfer-Encoding: 7BIT
Newsgroups: alt.gopher
Distribution: alt


  One of our greatest Gopher needs is the ability to cross-reference
documents.  For example, we have a document about fixing TN3270 problems
(located in a "computer problems" directory) that we might want to
cross-reference to a document on setting up TN3270 (located in a "computer
installations" directory), and other cross-reference to a document
describing unique services available using TN3270 (located in a "computer
services" directory).  It seems to me that a really good way of doing this
would be through HyperText links.

  The argument could be made that if the data was stored in the most
logical hierarchal structure, it would be easy to find and not need to be
cross-referenced.  Unfortunatly, not all people think the same way, and
what is a logical structure to one, may not be to another.  By setting up a
cross-referenceing system, the documents can be seperatly stored in the
most logical hierarcical structure, yet still be linked.

  To my knowledge this cross-referenceing ability does not exist yet in
Gopher.  Has anyone tried to set a standard for document-to-document
linking?

     - Brad Stone

---------------------------------------------------------------------
Brad Stone - Computing Support Coordinator - Brigham Young University
  Internet: Brad_Stone@byu.edu              BITNET: STONEB@BYUVAX
Date: Sun, 26 Jul 1992 06:58 MST
From: JONZY@CC.UTAH.EDU (Jonzy)
Subject: MacGopher0.5b1 now available
Original-To: gopher-news@boombox.micro.umn.edu
X-Envelope-To: gopher-news@boombox.micro.umn.edu
X-Vms-To: IN%"gopher-news@boombox.micro.umn.edu"
Newsgroups: alt.gopher
Distribution: alt

MacGopher0.5b1 is now available via the following methods:

Gopher Protocol:
	Host is augusta.cc.utah.edu port 70, you can retrieve either
	MacGopher.sit.hqx, which contains the new version of MacGopher
	along with the respective documentation, or go into the
	MacGopher directory and retrieve the individual items.

ftp:
	anonymous ftp to ftp.cc.utah.edu in /pub/gopher/Macintosh you
	will find MacGopher.sit.hqx


Bug fixes and program enhancements:
Fixed a bug that displayed garbage if nothing was available in a diretory.
Fixed a bug that caused the computer to get in a hanged state.
Fixed a bug that caused the program to crash when hitting an arrow key.

Added the ability to distinguish MIME, html, Image and TN3270 items, and 
changed the error icon.
Added a bookmark feature that currently supports text, directory, cso (ph), and 
telnet items.
Added command-period to abort the retrievel of an item.


Much of the code has been rewritten thus there may be some new introduced bugs.
So please send any and all bug reports to: jonzy@cc.utah.edu

I hope you enjoy.
-------------------------------------------------------------------------
Jonzy                                           | postmaster@cc.utah.edu
Postmaster (UUCC)                               | postmast@utahcca.bitnet
University of Utah Computer Center              | (801) 581-8810
-------------------------------------------------------------------------
President UHGA (Utah Hang Gliding Association)
-------------------------------------------------------------------------

Newsgroups: alt.gopher
From: heidis@sfsuvax1.sfsu.edu (Heidi Schmidt)
Subject: Conversion Confusion!
Organization: California State University, Sacramento
Date: Tue, 21 Jul 1992 14:54:54 GMT

We have experienced some difficulty in converting from Gopher 0.9 and
the Wais gateway to Gopher 1.01.  Any assistance would be appreciated!

Our Gopher data directory is: /usr/mail1/gopher
Our Wais directory is: /usr/support/wais/wais-sources

We tried creating a link to "test.src" using the example in server.c:

Name=Test
Path=waissrc:/usr/support/wais/wais-source/test
Type=7
Host=+
Port=+

This resulted in the error message: "File does not exist."

Then we tried creating a link using the example in the gopherd man
pages:

Type=7
Host=+
This resulted in the error: "Unknown index type."

We noticed that the gopherd man pages say that the indices should be in
tion of the link file?

We've tried a bunch of different things, but we just don't seem to get
it . . . Thanks in advance for your help.

Heidi Schmidt
San Francisco State University


P
Name=Test
Type=7
Path=7/usr/support/wais/wais-sources/test
Host=+
Port=+
From: emv@msen.com (Edward Vielmetti)
Newsgroups: alt.gopher
Subject: Re: official g2nntp
Date: 31 Jul 1992 12:22:21 -0400
Organization: Msen, Inc. -- Ann Arbor, Michigan
NNTP-Posting-Host: nigel.msen.com
X-Newsreader: Tin 1.1 PL3

I would like to see a g2nntp gateway that would let me reference articles
by message id, not just by article number.  That would increase the chance
that I could take a reference from a remote site and localize it without
having to copy the data back.

--Ed

Newsgroups: alt.gopher
From: doug@cc.ysu.edu (Doug Sewell)
Subject: Re: Newspapers on Gopher
Organization: Youngstown State University
X-Newsreader: Tin 1.1 PL4
Date: Wed, 29 Jul 1992 14:03:40 GMT

fkappe@fiicmds04.tu-graz.ac.at (Frank Kappe) writes:
: 
: I am looking for newspapers that are available on internet (through gopher or
: otherwise). So far I found the "Daily Texan" and "Minnesota Daily". Is anybody
: aware of any other newspapers (including non-english and non-gopherized ones)
: on internet?
: 
You might find some school, local or regional papers, but I don't know of 
any right off-hand.  The big ones (UPI news, USA Today, Washington Times, 
etc) are all handled by commercial usenet redistributors, and to make them
accessable to all comers via gopher (or nntp, for that matter) would cost
them revenues and potential customers, so their contracts prohibit making
them available.
--
Doug Sewell, Tech Support, Computer Center, Youngstown State University
doug@cc.ysu.edu	   doug@ysub.bitnet	<internet>!cc.ysu.edu!doug
"Recession: your friend loses his job.  Depression: you lose your job.
Recovery: Bush loses his job" - Bill Davidsen
From: moravan@yuma.ACNS.ColoState.EDU (Michael Moravan)
Newsgroups: alt.gopher
Subject: Branching out of the Gopher Directory Tree
Date: 24 Jul 92 20:15:58 GMT
Distribution: alt
Original-To: gopher-news@boombox.micro.umn.edu



I would like to have Gopher branch out of the gopher directory tree
to another subdirectory outside the gopher directory tree but in
the same unix file system. 

I am trying to bring up a Gopher 1.01 unix server  and found that gopher
will not follow a symbolic link and my system manager vetoed 
using a hard link.

One site appeared to use another port an the same gopher server?
Is this the only way to so this?

Michael
Newsgroups: alt.gopher
From: a-steiner@nwu.edu (Albert Steiner)
Subject: Re: index for all of gopherspace
Followup-To: alt.gopher
Organization: Northwestern University
Date: Mon, 27 Jul 1992 17:50:26 GMT

In article <1992Jul27.163746.974@nstn.ns.ca>, daniel@nstn.ns.ca (Daniel
MacKay) wrote:
> 

> Then- we just run an index on the abstracts, and gopher managers can put a
> search item onto their menus- something like "Gopherspace Resource Search"
> that points to the central registry.
> 
> Our hapless user picks it, and asks for "recipies" or "food" or "cooking"
> and gets a pointer back to the resource- whereever it is. (who cares where
> it is?)
, Canada
This is an idea I think is very important.  I would like to see a way to
encode an address in "about" entries for "important" directory levels. 
When the server selected an about entry with pointer, it would separate the
entry and the pointer into two items returned to the client.  The first
item is the about, the second item is a directory entry to the actual
location else where.

This still leaves the problem of verifying that the index's are up to date.
Perhaps they should be checked every week.  The original directory checked
again for its "about" file, the directory address added, and reposted in
the directory of directories.  In addition, new entries could be added by
mailing the address of a new "interesting" directory to the "index master"

Albert Steiner      a-steiner@nwu.edu     708-491-4056
Academic Computing and Networking Service
Northwestern University  2129 Sheridan Road
Evanston, IL  60208      USA