Well, my lunch date canceled, so … with this version, nb support is switchable:
notes_dir: ~/notes
default_extension: md # or org
exclude_dirs:
- denote
- .git
hide_hidden: true # hides .files when enabled
editor: micro # will be overridden with `nb edit` if nb_support == true
nb_support: false # if true, overrides your editor: setting and enables nb file management
So you can either just use cielagonote as a standalone note manager with no supporting ecosystem, or you can flip nb_support: to true and it’ll use nb’s native commands to create, rename, and delete notes, ensuring that nb’s underlying git repo stays clean and in sync with remotes.
One bit of config logic: if you enable nb support, the editor cn invokes will be based on your nb setting, not what you configured in .cnconfig.yml. That’s just to be compliant with nb’s expected behavior to keep the underlying repo clean.
… and there’s one tradeoff: nb’s daily plugin expects you to just provide it with an input argument and logs the entry for you in the daily note. I wasn’t aware of the daily plugin when I started using nb and settled into my own daily-yyyy-mm-dd.ext convention. I think there’s a way to address the whole thing that leaves both approaches intact if you choose to turn on nb_support, but for now the README just says “don’t use the ^t keystroke if you’re using nb because it doesn’t honor the nb daily file naming convention.”
I think I’ll stop messing with it for a while now. It does what I want either as a standalone tool for anyone, or as a way to use nb with a slightly different twist on its native behavior. There is an fzf plugin for nb that gives you a fast way to access notes, cielagonote just adds a few conveniences so you can stay in its interface and manage notes a little more visually and a little less “dig up a number, enter a number” to do operations.
Update: Oops. Introduced a regression. 0.7 is the way to go: