Actually, this might have to do with Geir's new Mac!!! "New line" sequences in: Linux => "\n" or "\x0A" Windows => "\r\n" or "\x0D\x0A" Mac => "\n\r" or "\x0A\x0D"
With all the smart tools (CVS stuff included) editing Velocity's text and trying to convert between one OS sequence to the other, I wonder if one of them is not loosing the right sequence somewhere. It is even worse if the tool is only trying to interpret a bit of the text, like it happens with a diff or an editor that just changes what it edits. The usual mix was Windows + Linux. With a new sequence added to the mix, maybe something went wrong somewhere... and maybe it got wrong in more than one step. (I am imagining these sequences going from tool to tool and being processed like the state of some weird random state machine.) Have fun, Paulo > -----Original Message----- > From: Donnie Hale [mailto:[EMAIL PROTECTED]] > Sent: Saturday, January 05, 2002 9:04 PM > To: Velocity Developers List > Subject: RE: [ANN] Struts + Velocity + Tools +... > > > Gabe, > > Thanks for letting me know that I'm not going crazy. :) FWIW, in VS I do a > regex global search&replace from "\x0D\x0D\x0A" to "\x0D\x0A". If there's > anything I can do to help (apart from pointing out work for you > and Geir ;), > let me know. > > Donnie > > > > -----Original Message----- > > From: Gabriel Sidler [mailto:[EMAIL PROTECTED]] > > Sent: Saturday, January 05, 2002 1:53 PM > > To: Velocity Developers List > > Subject: Re: [ANN] Struts + Velocity + Tools +... > > > > > > Donnie Hale wrote: > > > > > > Gabe and Geir, > > > > > > I use Visual SlickEdit. When I open a file that has the > problem, it has > > > extra blank lines with one of those funny characters at the > start of the > > > next non-blank line. VS has no problem opening DOS or Unix files in a > > > correct way automatically - I do it all the time (been using VS > > for 8 years, > > > so I know it really well). When I see that problem, I look at > > the file in > > > hex mode, and that's how I know that the lines end with > "\x0D\x0D\x0A". > > > Additionally, not every ASCII file in the velocity-tools > distro has the > > > problem. About 1/2 of them (maybe more than 1/2) are perfectly > > fine. I can > > > open one and see the problem then open the next file in the > > same directory > > > and it's OK. > > > > > > Don't know what to tell you, but I'm sure the lines end that > > way. I don't > > > know UltraEdit, but I'm betting it tweaks the line terminators > > when it opens > > > the file. ?? > > > > > > > Yes, you are right. UltraEdit is tweaking them. Now I know how to > > look for the > > problem but not yet how to avoid it. Must be the Geir's Mac that > > interferes... ;-) > > > > Gabe > > > > > > -- > > Gabriel Sidler > > Software Engineer, Eivycom GmbH, Zurich, Switzerland > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
