ex program inserts null char for newline upon insert/append of backslash newline

2010-07-28 Thread Frush
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

Re: ex program inserts null char for newline upon insert/append of backslash newline

2010-08-10 Thread Frush
= '\\')) This patch seems to be the cause of the behavior we're seeing. Can someone (VIMBOSS?) more familiar with this comment on this behavior, and if it correct for ex? -- Ray Frush IT Infrastructure Engineer > To recreate the problem, perform the following at the ba

Re: ex program inserts null char for newline upon insert/append of backslash newline

2010-08-11 Thread Frush
Thanks for the replies and the insight into folk's focus on bug smashing for 7.3. Perhaps this will be of interest to that effort: I got this hint from another source: Apparently in FreeBSD, VIM 7.2 with a select set of patches manages to get the behavior correct: Does not occur in: VIM -

Re: Patch 7.3.014

2010-11-17 Thread Frush
I managed to miss this posting until now, so I'm only 45 or so days late. I appreciate that you kept this request in the queue and worked on it after the release of 7.3! I've tried this with VIM (EX) 7.3.62, and it still produces a different result than the 6.3 version we're running on RHEL4.

Re: Patch 7.3.014

2010-12-09 Thread Frush
Any further thoughts on this behavior bug? On Nov 19, 2:51 pm, Ray Frush wrote: > On Fri, Nov 19, 2010 at 2:20 PM, Bram Moolenaar wrote: > > > What is the :version output of the HP-UX version? > > $/usr/bin/ex > :version >  HP Version 82.6.1.14 $ 32-bit NLS $ > >

Re: Patch 7.3.014

2010-11-18 Thread Ray Frush
Bram, et al- The main complaint here is that the current versions of vim/ex (7.x) crushes the \ (Backslash newline) to a , 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,

Re: Patch 7.3.014

2010-11-18 Thread Ray Frush
, Nov 18, 2010 at 2:15 PM, Bram Moolenaar wrote: > > Ray Frush wrote: > > > To recreate the problem, perform the following: > > cat - > ex.input << EOF > > a > > X \\ > > Y > > . > > w ex.output > > EOF > > cat -tvse e

Re: Patch 7.3.014

2010-11-19 Thread Ray Frush
OK, I never noticed this before, but apparently we're running VIM 5.8 on our HP-UX boxes. On Fri, Nov 19, 2010 at 2:20 PM, Bram Moolenaar wrote: > > > > What is the :version output of the HP-UX version? > > $/usr/bin/ex :version HP Version 82.6.1.14 $ 32-bit NLS $ We also have the VIM editi