In article <199511091817.SAA02868@di_frueauf.ira.uka.de> frueauf@ira.uka.de writes:
>
>>Number:         1749
>>Category:       bin
>>Synopsis:       /usr/bin/vi can't handle ":r ~user/something" correctly
>>Confidential:   no
>>Severity:       serious
>>Priority:       medium
>>Responsible:    bin-bug-people (Utility Bug People)
>>State:          open
>>Class:          sw-bug
>>Submitter-Id:   net
>>Arrival-Date:   Thu Nov  9 14:50:03 1995
>>Last-Modified:
>>Originator:     Thorsten Frueauf
>>Organization:
>private
>>Release:        <NetBSD-current source date> NetBSD current from 08.11.1995
>>Environment:
>	
>System: NetBSD di_frueauf 1.1_ALPHA NetBSD 1.1_ALPHA (Milano) #8: Thu Nov 2 16:29:47 GMT 1995 milano@di_frueauf:/home/milano/source/netbsd-src/sys/arch/amiga/compile/Milano amiga
>
>
>>Description:
>	
>vi can't resolve the ~ when your try to include a filename referenced indirectly
>by ~user. Somehow some "crap" gets before the resolved pathname.
>
>>How-To-Repeat:
>	
>
>Assuming ~user/foo exists and is a valid textfile, readable by the one that
>trys to include it. Now start vi then ":r ~user/foo", you will get:
>
>Error: ^[[H^[[2J/home/user/foo: No such file or directory.
>
>If you try ":r /home/user/foo" the file gets included like expected.
>

This is not a bug with vi. Your .cshrc is busted and has 'clear' or some
other junk writing to the terminal...

You should protect such portions with $?prompt... This does not work all
the time but it should be good enough.

christos