If you redirect Vim input it will read commands from there. If the
stdin actually contains text use the "-" argument, e.g.:
ls . | vim -
If you redirect Vim output you get the message you mentioned. You then
can't see what you are doing, but you can still edit.
Try typing ":qa!". If only output was redirected it should get you out
of the stuck situation.
If both input and output are redirected, you are really stuck.
--
I'm sure that I asked CBuilder to do a "full" install. Looks like I got
a "fool" install, instead. Charles E Campbell, Jr, PhD
/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
I was previously using Vim 7.2 with the following:
file fixnbsp.vim contained:
:%s/> />\ /g
:%s/ </\ </g
:wq
and a shell script under Cygwin with the following snippet:
# Build new compares.
for f in $(cat $ALLFILES); do
if [ -e new/$f ]; then
c:/Program\ Files/Beyond\ Compare\ 2/BC2.exe @shortcompare.txt $f
c:/Program\ Files/Vim/vim72/vim.exe -S fixnbsp.vim compares/$f.html
fi
done
A nearly identical setup (substitute vim73 for vim72) outputs:
Vim: Warning: Output is not to a terminal
Vim: Warning: Input is not from a terminal
Reading :help 26.4 and the examples, I changed fixnbsp.vim to:
%s/> />\ /g
%s/ </\ </g
write
quit
and the vim step in the loop to:
c:/Program\ Files\ \(x86\)/Vim/vim73/vim.exe -e -s
compares/$f.html < fixnbsp.vim
which is the same as the example:
vim -e -s $file < change.vim
(obviously, I changed the "write tempfile" to just "write" since I
want to change in place)
This just seems to hang. (possibly on the write?)
I know I could use sed, but I would just like to know whether
something changed in Vim 7.3 that changed this behavior, and what I
could do to make this work.
BTW, from http://www.vim.org/maillist.php#vim clicking the "tips
archive" from the "Comments" section gives a 404.
Fuzzy
One last try... I can go look over several hundred patches, but I was hoping someone might have an idea. Any thing I should look for?