Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 (Fortune 01.1b1); site graffiti.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!ut-sally!ut-ngp!shell!graffiti!peter
From: peter@graffiti.UUCP (Peter da Silva)
Newsgroups: net.bugs.4bsd
Subject: Re: vi bug(feature?)
Message-ID: <154@graffiti.UUCP>
Date: Mon, 2-Sep-85 09:13:02 EDT
Article-I.D.: graffiti.154
Posted: Mon Sep  2 09:13:02 1985
Date-Received: Wed, 4-Sep-85 06:25:39 EDT
References: <144@peregrine.UUCP> <33500005@ctvax>
Organization: The Power Elite, Houston, TX
Lines: 13

> Reason 8491 why I hate csh(1):
> The solution is to fix csh(1) so that it does not print the
> prompt string on non-interactive shells.  I have fixed my csh(1)
> to do just that.

No need to do this, just don't set the prompt string in your .cshrc, since
CSH doesn't set the prompt string on non-interactive shells. In your
.cshrc you can tell if the shell is interactive or not and act as follows:

if ( $?prompt ) then
	set prompt=...
	blah blah blah
endif