I’ve used roughly this (minus the GUI) for bug-hunting sessions (one file per issue), which makes it pretty share-able too (copy- & paste into an issue tracker comment). Inserting dates is smart, maybe it could have a rfc3339-with-timezone format for extra share-ability.
Did you think about supporting editing notes, or is it a design choice to “go immutable”?
Will take this for a ride (possibly tinkering with adding vim bindings) – thanks for sharing!
I was thinking that append-only and immutable would be the best. After all, you can always edit the markdown file directly (have to restart the server, though). But in principle, I guess it’s not a big deal, and it should be trivial to have an “edit” button which just “converts” a note into a textarea. The notes are stored in memory on the server side, and after an update it would just rewrite the whole file.
I’ve used roughly this (minus the GUI) for bug-hunting sessions (one file per issue), which makes it pretty share-able too (copy- & paste into an issue tracker comment). Inserting dates is smart, maybe it could have a rfc3339-with-timezone format for extra share-ability.
Did you think about supporting editing notes, or is it a design choice to “go immutable”?
Will take this for a ride (possibly tinkering with adding vim bindings) – thanks for sharing!
score 2 · canonical
I was thinking that append-only and immutable would be the best. After all, you can always edit the markdown file directly (have to restart the server, though). But in principle, I guess it’s not a big deal, and it should be trivial to have an “edit” button which just “converts” a note into a textarea. The notes are stored in memory on the server side, and after an update it would just rewrite the whole file.
score 2 · canonical