#fs #tempfs


A Rust implementation of the txtar Go package

5 releases (1 stable)

1.0.0 Jun 2, 2022
0.2.2 May 15, 2022
0.2.1 May 15, 2022
0.2.0 May 15, 2022
0.1.0 May 13, 2022

#728 in Filesystem

Download history 3/week @ 2024-02-25 2/week @ 2024-03-10 73/week @ 2024-03-17 4/week @ 2024-03-24 181/week @ 2024-03-31

260 downloads per month
Used in diffedit3


256 lines


crates.io version docs.rs docs license

A Rust implementation of the txtar Go package.

cargo add txtar


let txt = "\
-- file1 --
File 1 text.
-- foo/bar --
File 2 text.
-- empty --
-- noNL --
hello world";

let archive = txtar::from_str(txt);

Txtar goals

As described in the Go package:

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.

Txtar format spec

The format spec as written in the txtar Go package source code:

Txtar format

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.


MIT OR Apache-2.0


~19K SLoC