Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!bu-cs!buengc!bph
From: bph@buengc.BU.EDU (Blair P. Houghton)
Newsgroups: comp.unix.questions
Subject: Re: Two vi questions.
Summary: I flame myself.
Message-ID: <4107@buengc.BU.EDU>
Date: 10 Sep 89 04:40:23 GMT
References: <4237@ncar.ucar.edu> <3937@mentor.cc.purdue.edu> <614@jvncf.UUCP> <4092@buengc.BU.EDU>
Reply-To: bph@buengc.bu.edu (Blair P. Houghton)
Followup-To: comp.unix.questions
Distribution: usa
Organization: Boston Univ. Col. of Eng.
Lines: 43

In article <4092@buengc.BU.EDU> bph@buengc.bu.edu (Blair P. Houghton) writes:
>I've always wanted to get ahold of a real vi source and fix it so
>that the :r and :w commands do a system call that uses sh to do
>its globbing.  Then again, for all I know it's actually passing the
>ex-commands (commands that start with a colon) unglobbed to ex, and
>it's ex that I need to fix.

No, it's ME I need to fix.

for the past forever, I've been having that problem.  Now I am told
that vi does indeed pass the globbing onto csh, and that it's only
because I am to bonehead-f****ing lazy to put

    if ( $?prompt ) then
	set prompt="subwhat? "
    else
	unset prompt
    endif

in my .cshrc that I am having this problem, because csh is returning
my subshell-prompt (my csh prompt is "what? ") to vi, which then
thinks I want it as a file, in addition to the file csh probably
properly globbed...

Excuse me.

(Shuffle, pad, pad, pad, bend, wrench-CLANG! "ouch" wrench-CLANG! "ouch"
wrench-CLANG! "ouch"...)  [Repeat until either head or wastebasket
is dented beyond recognition.]

PLUS, I use the $?prompt feature on another machine, on which I have
done plenty of editing, but was so ingrained by my ignorance and sloth
("drat, there's that prompt coming back in the output from a
pipe-command again, one of these days I gotta put that $?prompt
condition in my .cshrc," I have said to myself almost daily...) on this
one that I never noticed that globbing would work.

				--Blair
				  "...an elephant is warm and mushy..."

P.S. AND I managed to delete the message from the kind person
who told me this was the likely cause, so all I can say is
"thank you, eirik@labs.labs.tek.com, whoever you are"...