VIM Developers-
One of the engineers in our lab found this one, and even wrote up a
simple test case. Apparently, some change was introduced in VIM 7.0
that changes the behavior of the 'ex' command. I wasn't able to
quickly find a VIM bugtracker, so if there is one, please point me
there so I can submit this issue!
This problem occurs on version 7.0.109-7 of vim on RHEL 5. It also
seems to occur on a self-compiled 7.2 version (VIM - Vi IMproved 7.2
(2008 Aug 9, compiled Jul 28 2010 12:12:14))
The problem occurs both when executing ex from a script (as in the
example shown below) or in an interactive ex session, but not with a
vim interactive session.
The problem did not occur with VIM 6.3.
To recreate the problem, perform the following at the bash command
prompt:
#Create Input file to ex
cat - > ex.input << EOF
a
X \\
Y
.
w ex.output
EOF
# Show input
cat -tvse ex.input
# Submit input to ex
ex - -u NONE < ex.input
#Show output
cat -tvse ex.output
When working correctly VIM 6.3 (rhel4), the output from cat of
ex.output is:
$
X \$
Y$
On VIM 7.x , the output from cat of ex.output is:
X \...@y$
Note that the '^@' indicates that we have a null character where there
should have been a newline.
Hopefully someone familiar with the code will be able to track down
where this is getting messed up.
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
