Ideally, a prose editor would be a minimalistic WYSIWYG editor, where each formatting option mapped to a feature of Markdown. The "document format" would, internally, be a Markdown document stored in a git repository—but actual Markdown text would be escaped if pasted into the editor itself, so this would just be an implementation detail (except if you tried to copy-and-paste from the editor to a plain textarea—then you'd get Markdown, which is better than losing formatting altogether.) The editor would auto-commit each and every change; undoing and then typing something else would create a branch.
Other people could work on a document/repo with you; the editors would P2P-send operational transformations when they knew that others had the same document open in the editor, with eventual consistency guaranteed by committing the changes to the repo asynchronously (where each user is committing their current view of the operationally-transformed state, so no git-level non-fast-forward merges are needed, unless the users are actually working on purposefully-made separate branches.)
I haven't used TextMate, so can't compare the two, but E is far superior to any of the other text editors I've tried.
The project view is just straight Windows Explorer, so you can use TortoiseSVN or Git GUI quite easily.
www.macromates.com