Micah Jerome Ellison

> One might think a little bit about consistency. For example, if jrnl is started the first time, right now a default (english; mm-dd-yyy) format string is used. If the...

I did some work on this six months ago with PR #1378, but ran into a variety of issues and I am having a hard time mustering the drive to...

Hi @SepehrRasouli, sorry for the late response. Do feel free to submit a PR if you're interested in working on this. Just please be careful for anything that impacts the...

Thanks for posting this idea. Unfortunately, there's no built in functionality for this. Right now, there are two main barriers to implementing it in a markdown export: * It seems...

I agree @eshrh that constraining this concern to markdown makes it a lot simpler. The anchors sound like an elegant solution, and "YYYY-MM-DD_entry-name" should work in 99.9% of the situations...

It sounds like we'd have to drive this through a config field like the OP mentioned, or else it would be a breaking change -- for instance, if someone ends...

Hi there, thanks for submitting this. We have been thinking about adding support for attachments for some time, though there are lots of data format issues we'd like to work...

Thanks for the filing this bug and providing all this information. I think the best way to deal with this (if anyone is interested in resolving this before we get...

Hi @dcg929, thanks for reporting. It looks like jrnl creates an empty file on startup, and empty files can't be decrypted since there is nothing to decrypt. Instead of creating...

Oh, forgot to mention the workaround! If you delete your original empty journal file (which you can find by running `jrnl --list`), you should be able to get past this...