Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.7.0.7 $; site waltz
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!inuxc!pur-ee!uiucdcs!convex!waltz!ramey
From: ramey@waltz
Newsgroups: net.bugs.4bsd
Subject: Re: vi bug(feature?)
Message-ID: <32700001@waltz>
Date: Mon, 29-Jul-85 10:01:00 EDT
Article-I.D.: waltz.32700001
Posted: Mon Jul 29 10:01:00 1985
Date-Received: Fri, 2-Aug-85 06:37:09 EDT
References: <144@peregrine.UUCP>
Lines: 17
Nf-ID: #R:peregrine.UUCP:-14400:waltz:32700001:000:936
Nf-From: waltz!ramey    Jul 29 09:01:00 1985


I remember seeing the filename expansion from vi (or mail, or ...)
before.  We finally tracked down the problem to the fact that when
the csh was called to do the echo, it first printed out the prompt,
then the output of the echo, then the prompt again.  Note that this
only happened when you have a `set prompt ...' in your .cshrc.
If you use the default prompt, or set the prompt in your .login, there
was no problem.  Seems the csh knows it shouldn't print the prompt
in a non-interactive shell.  Instead of using an if statement around
the prompt printing code, they just don't give the prompt an initial
value, so the csh prints out a null prompt.  So, if you set your prompt
in the .cshrc file, the prompt is echoed.  The fix to the csh source
is easy; if you don't have source, just don't set the prompt in the .cshrc
(or as was pointed out before, only set the prompt in an interactive shell).

Joe Ramey
convex!smu!waltz!ramey