Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: armltd!jbiggs@relay.eu.net (John Biggs)
Newsgroups: comp.sys.sun
Subject: Re: File completion in csh
Keywords: Miscellaneous
Message-ID: <2287@brchh104.bnr.ca>
Date: 2 Apr 91 15:00:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 20
Approved: Sun-Spots@rice.edu
X-Original-Date: 28 Mar 91 15:18:37 GMT
X-Refs:  Original: v10n63
X-Sun-Spots-Digest: Volume 10, Issue 75, message 1
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

tml@goanna.cs.rmit.oz.au (Timothy Liddelow) writes:

>Why is it that on my distributed SPARC system that when file completion in
>csh is set, it doesn't work properly ?  If escape is pressed on the
>command line, the command is simply not recognised.  This only happens on
>the client machine, not the server.  As the file completion must obviously
>read the current directory, could that be the problem that my machine has
>to read the remote disk ?

I too have found that filec does not work in a cmdtool (which uses the
sun-cmd termcap entry).  It appears that whilst pressing ESC does actually
perform the file completion it also has a similar effect to pressing ^U as
the command line is nullified but not erased from the screen.  This can be
proved by having a look at the command history which shows now record of
the command being typed.  What I have discovered is that rlogging into
your own machine does in fact cure the problem and filec works perfectly,
although I am still using the same sun-cmd termcap entry. So what
difference does it make rlogging into your own machine? 

--John Biggs (jbiggs@armltd.uucp)