I sat for a day with the nb daily plugin support question, a little torn:
- I do not like the daily file-naming convention (
yyyymmdd.ext), especially since other files have datestamps in the names. - I much prefer the
daily-yyyy-mm-dd.extfor scanability and fuzzy-finding, and I like the way cielagonote titles the daily file, which matters in some parts of the Markdown ecosystem.
So my initial approach was to tell nb people to just not expect the daily functionality to work in cielagonote, or that they’d just get a daily-yyyy-mm-dd file dropped in their nb instance that wouldn’t work with the daily plugin. I didn’t like that much.
I had a fork of the nb daily plugin anyhow so that I could have my preferred file-naming convention for daily notes using stock nb and I’ve added some configuration logic that lets people go a few ways:
- Use completely stock nb and its daily plugin in or out of cn. On first daily entry of the day, you get dropped into a command line where you can type in your first log.
- Use stock nb with the forked plugin and get the same behavior, but with a more readable file naming scheme.
- Don’t use nb and get the more readable file-naming scheme.
This is all managed with a new daily_format: setting that can be set to either nb or cn to drive how files are named.
Personally, I’m going to use the forked plugin so I can keep using nb for management and git syncing but have more legible filenames for daily notes.
You can install it from the command line with the URL and use it either in the context of cielagonote or just use it alone to pretty up your daily note filenames:
nb plugin install https://github.com/pdxmph/cielagonote/blob/main/extras/cn-daily.nb-plugin