On 4/18/06, John Szakmeister <john@szakmeister.net> wrote:
> On Tuesday 18 April 2006 00:15, Ivan Zhakov wrote:
> > On 4/18/06, Peter N. Lundblad <peter@famlundblad.se> wrote:
> > > Garrett Rooney writes:
> > > > On 4/17/06, Peter N. Lundblad <peter@famlundblad.se> wrote:
> > > > > Garrett Rooney writes:
> > > >
> > > > I was assuming that each entry had a fixed number of fields or
> > > > something like that. If not, I imagine we could include some specific
> > > > character as the end of entry marker...
> > >
> > > After some discussion with rooneg on IRC, I'm going to change the format
> > > so that newlines separate fields instead of pipes and the sequence "\f\n"
> > > (control-l newline) will terminate each record.
> >
> > What is \f means? Did you mean "\r\n"?
>
> '\f' is the form-feed character (it advances to the next page when printing).
>
> >
> > > Can everybody live with this change?
> >
> > -0.5, I cannot. IMHO such format could be broken by many editors. I
> > often tweak entries file for debugging.
>
> Doubtful... they're present in the source code right now, and your editor
> seems to be doing fine. :-) Take a look just below the copyright header, and
> you'll find one. Just below #includes, you'll find another. Most editors
> I've come across seem to work fine with the form-feed character.
Oh, sorry. Ok, I am removing my vote, if it's new page separator. I've
investigated.
--
Ivan Zhakov
Received on Tue Apr 18 09:44:05 2006