Bram, et al-
The main complaint here is that the current versions of vim/ex (7.x) crushes
the \<newline> (Backslash newline) to a <null>, which is shown as a "^@" in
the output of cat -tvse.
Our reference 'ex' version is from HP-UX 11.x. The output of VIM 6.3 and
the reverence vi agree, but from VIM 7.0 on, we get the \<newline> =
<nul>. I've recompiled 6.3 on our RHEL5 systems, and have confirmed that
6.3 produces the expected reference output.
My goal is to get VIM 7.x to match the 6.3, and by extension the reference
'ex' behavior.
A number of files use the \<newline> construct, for example the NIS netgroup
file:
build1 (pdbuild0.tech.net,-,pd) \
(pdbuild1.tech.net,-,pd) \
(pdbuild2.tech.net,-,pd) \
(pdbuild3.tech.net,-,pd) \
(pdbuild4.tech.net,-,pd) \
(pdbuild5.tech.net,-,pd) \
(pdbuild6.tech.net,-,pd) \
(pdbuild7.tech.net,-,pd) \
(pdbuild8.tech.net,-,pd) \
(pdbuild9.tech.net,-,pd)
At $WORK, we have a number of scripted processes that chew on files that
look like this, and when the \<newline> gets converted to a <nul>, the
resulting output is incorrect.
So, I would submit that a \<newline> should be output as \<newline> by ex.
Have a look at ex.input:
>
> a$
> X \$
> Y$
> .$
> w! ex.output$
>
>
> You have a backslash at the end of the line. That means the line break
> is taken literally. You need to double the backslash if you want a
> backslash at the end of the line.
>
> My old "original vi" doesn't run right now, thus I can't verify how it
> handles this. It's a bit difficult to tell what would be the correct
> way to handle this.
>
> --
> The chat program is in public domain. This is not the GNU public license.
> If it breaks then you get to keep both pieces.
> -- Copyright notice for the chat program
>
> /// Bram Moolenaar -- [email protected] -- 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
> ///
>
--
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
