Package txtar implements a trivial text-based file archive format.
The goals for the format are:
- be trivial enough to create and edit by hand. - be able to store trees of text files describing go command test cases. - diff nicely in git history and code reviews.
Non-goals include being a completely general archive format, storing binary data, storing file modes, storing special files like symbolic links, and so on.
A txtar archive is zero or more comment lines and then a sequence of file entries. Each file entry begins with a file marker line of the form "-- FILENAME --" and is followed by zero or more file content lines making up the file data. The comment or file content ends at the next file marker line. The file marker line must begin with the three-byte sequence "-- " and end with the three-byte sequence " --", but the enclosed file name can be surrounding by additional white space, all of which is stripped.
If the txtar file is missing a trailing newline on the final line, parsers should consider a final newline to be present anyway.
There are no possible syntax errors in a txtar archive.
Format returns the serialized form of an Archive. It is assumed that the Archive data structure is well-formed: a.Comment and all a.File[i].Data contain no file marker lines, and all a.File[i].Name is non-empty.
func NeedsQuote ¶
NeedsQuote reports whether the given data needs to be quoted before it's included as a txtar file.
Quote quotes the data so that it can be safely stored in a txtar file. This copes with files that contain lines that look like txtar separators.
The original data can be recovered with Unquote. It returns an error if the data cannot be quoted (for example because it has no final newline or it holds unprintable characters)
An Archive is a collection of files.
Parse parses the serialized form of an Archive. The returned Archive holds slices of data.