Alex Fikl

> So I'm ok with keeping both (with rename mostly being a wrapper around `mv`). It's a bit like `papis tag` is just a more convenient version of `papis update`....

That's a very large chunk of hopeful fixes. My recommendation would be to split it up into smaller PRs: would be easier to review and more likely to get some...

> Oh i completely miswrote my intentions. What I'd like in this PR is to work on the quickstart/sample workflow/overview issues. So, give a birds-eye view of what you can...

> Since the users that would eventually use papis are already somewhat familiar with the command line, I skipped speaking of so common command-line patterns. Like define what a flag...

This was a bug in the type annotations that was fixed in https://github.com/python/typeshed/commit/edf41ae5e239d92a5c063179842062f2bc368ed8. It should be in the 1.10 release of mypy. We can use this to shut up mypy

We could also add a `# type: ignore[error-code?]` in there to support older mypy? That makes it clear it's just a typing error and the code is ok. > Probably...

> I'd rather not ignore the type error, unless there's a way of gating it to older `mypy` releases -- after all, that line might one day contain a different...

I don't think there's any particular reason for that, since I'm not sure if there's any official list of allowable characters for BibTex / BibLaTeX / Biber. If it works,...

Added some clearer docs in #714 to mention that the references are going to be cleaned up. Hopefully other people will avoid some confusion with that!

Always a big fan of improving the docs! Those all sound like good ideas to me and I'm happy to help :grin: (but yeah, not the best writer either) To...