basic_io format merged

[Martin Pool]

On 25 Nov 2005, John A Meinel <john at arbash-meinel.com> wrote:
> I might play with this.
> It would be nice if it allowed for a custom prefix per line (since I am
> writing everything after a # to make it obvious that it is a comment).
> But I can always iterate over its output and do that myself.
> 
> I do prefer the looks of text without the double quotes.
> 
> If we left justify the keyword names, then we can use a leftmost space
> to indicate that we are wrapping lines.
> And having text starting on character 1 will terminate the text, rather
> than a blank line.
> 
> Think of it like patch.

Yep, I'll change it to do that.  Or maybe a tab would be better than a
space?

> The only other thing we need to think about is how to handle text that
> doesn't end in a newline.

Do you mean in this format, or in the changeset diffs?  GNU diff
represents them by putting the literal line "\ No newline at end of
file".

As for the rfc822-like format, I suggest that strings normally do not
have a trailing newline.  Those that do will span multiple lines, with
continuation marks.  So "hello\nworld\n will be"

message: hello
\t	world
\t

\t would be a real tab.

-- 
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051128/98c67ad6/attachment.pgp