Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site gitpyr.UUCP
Path: utzoo!linus!gatech!gitpyr!robert
From: robert@gitpyr.UUCP (Robert Viduya)
Newsgroups: net.bugs.4bsd
Subject: Re: vi bug(feature?)
Message-ID: <602@gitpyr.UUCP>
Date: Sat, 27-Jul-85 09:09:29 EDT
Article-I.D.: gitpyr.602
Posted: Sat Jul 27 09:09:29 1985
Date-Received: Sun, 28-Jul-85 08:15:24 EDT
References: <144@peregrine.UUCP>
Distribution: net
Organization: Georgia Tech, Atlanta
Lines: 27
Summary: vi and shell escapes with csh

In article <144@peregrine.UUCP>, mike@peregrine.UUCP (Mike Wexler) writes:
> My standard shell is the /bin/csh.  When I try doing a any command
> with a name that needs to be shell expanded the editor calls the shell,
> but gets confused by the shell prompt and includes that in the file list.

The problem isn't in vi, but in csh.  Whenever csh starts up as a non-
interactive shell, it unsets the prompt variable.  An unset prompt var-
iable will never get mixed up in other program output.  If your .cshrc
file goes ahead and sets the prompt then it will print out the prompt
when it thinks it's supposed to.  The solution, in your .cshrc, is to
check if the prompt is already set to something ('% ') and, if it is
then set it to what you want it to be, otherwise leave it alone.  The
following is similar to what I have in my .cshrc:

    if ${?prompt} then     # don't set prompt if not set (only with -c/-t flag)
	set prompt="Prompt> "
    endif

Hope this helps....

					robert
-- 
Robert Viduya							01111000
Georgia Institute of Technology

...!{akgua,allegra,amd,hplabs,ihnp4,masscomp,ut-ngp}!gatech!gitpyr!robert
...!{rlgvax,sb1,uf-cgrl,unmvax,ut-sally}!gatech!gitpyr!robert