I almost really like this tool. It's close to being seamless and Unixy, offering a pretty small command-line-option-language that expresses a bunch of journal-related commands. I like that idea, a lot. But the recipes dive right into piping text through wc and grep, so I wonder: what exactly does this offer over some bash functions and raw textfiles? I've already got cat, grep, find, tail, xargs et al.
More nitpicking: the * escaping bothers me. That's a core feature, using the * to mark things, but you have to avoid letting bash expand it. Are there any better characters? Does 'single quoting' help anything?
The fuzzy date parsing looks great. (: I also think the no-dash (new entry) vs dash (filters..) vs double-dash (action) convention is fairly neat as far as calling conventions go. Tagging things with @ seems like a useful convention, too, even if I end up using notepad.
Thanks :) In fact, jrnl started as exactly that: some bash functions over a text file. But then I wanted encryption. And I wanted fuzzy date parsing. There we go...
I agree that the * is not perfect. Turns out there aren't so many characters that are accessible on most keyboards (also non-US layouts) that are NOT already special characters on most shells. Suggestions welcome!
More nitpicking: the * escaping bothers me. That's a core feature, using the * to mark things, but you have to avoid letting bash expand it. Are there any better characters? Does 'single quoting' help anything?
The fuzzy date parsing looks great. (: I also think the no-dash (new entry) vs dash (filters..) vs double-dash (action) convention is fairly neat as far as calling conventions go. Tagging things with @ seems like a useful convention, too, even if I end up using notepad.