Alex Fikl

> I just tried your fork because I need this feature, but I somehow can't start the `ref-format` with a lowercase letter. I'm using this Jinja format string: > >...

@hermlon Turns out my case was just a config error. I added a test for the case you mentioned (I think), i.e. setting a `ref-format.jinja2`, and it seems to work...

> I tried the commit [126825c](https://github.com/papis/papis/commit/126825cb47cb2745e12779e1839aa7a2952a7dcf); it works well, no abnormalities found yet. 👏 Awesome! Thank for you testing! > One thing is that something like `papis update --set ref.jinja2...

@OopsYao The latest version should also support `papis update --set ref.jinja2 [format]`. Let me know if you try it and something doesn't work (I just very briefly tested it)!

> Great work! I tried `papis update --set` with something like `tags.jinja2` as well as `ref`, `publisher` and etc. They all work as expected. Thank you! Glad to hear that...

> I have been trying this feature for a couple of weeks and I really like it! @kiike Thank you for trying this out! :heart: > While the config is...

> Yes. Having to define manually all of them from scratch is quite a drag. Plus it's not straightforward to see the changes without being put off by all the...

I was just looking at this a bit and it seems to be pretty complicated to fix in a satisfying manner. One thing to note is that `papis init` is...

@hseg #741 should be an improvement in this direction. Can you test if it works for you?

> The problem of `papis` creating the config directory, then warning that it might overwrite the config it's already created still persists: Gave this another go and silenced all the...