4 ms·

I really love this. One nit I must pick, however, is with the "just-so" nature of the journal screenshots. I see something similar in pinterest-style "bullet jo

I really love this. One nit I must pick, however, is with the "just-so" nature of the journal screenshots. I see something similar in pinterest-style "bullet journal"/habit tracking colourful journal layouts (example[0]). Specifically, these look nice (or work) only if your to-do list is just so, usually fairly short and with really short items on it. So the "demo" versions of these have mocked up content which fits vs. real content, which is frequently less uniform. In this article, you'll see the demo content is a lot of "buy apples" and "make apple pie," but note that no to-do items exceed 18 characters which is the maximum length to fit nicely in that layout. So if you need to "buy turkey baster" (18c) you're OK, but if you need to "return turkey baster" (21c) you've overflowed the layout. Likewise, you can "call Alexander" (15c) but "send thank you card to alexander and elizabeth" (46c) is way over budget, and you'll need to mutilate it down to "ty card alex&beth" (18c) to fit. This leads, in the example, to shortening items to something like "shopping trip," at which point too much context is lost (what if you have a second shopping trip?). Likewise, if you want to dump all the todos you can think of for the week and it's 20 or 30 small items, it's not clear that would work well in these layouts. This is not to malign this system which I think is really cool, but to suggest that it's more useful to see real and more varied content in a system like this to see how it "really looks" rather than exclusively made-to-measure content of 1-6 super-short items per list. 0: https://anjahome.com/summer-bullet-journal-ideas/#What_Is_a_Bullet_Journal https://anjahome.com/summer-bullet-journal-ideas/#What_Is_a_...

jvanderbot 3y ago
I agree. I suspect with some level of curmudgeonness that it's because author calls themself a pixel-artist. I have a brutalist CLI/programmer take on bullet journalling from vim, just for comparison: https://jodavaho.io/posts/bash-journalling.html https://jodavaho.io/posts/bash-journalling.html https://jodavaho.io/posts/bullet-journalling.html https://jodavaho.io/posts/bullet-journalling.html It is essentially: - One hidden folder for journal entries - Each entry is a file of the form YYYY-MM-DD.md - A bash alias will open today's file (or "yesterday" or "next thursday" or "2 weeks") using the date cli util - A few vim formatting steps make the already-well-functioning github markdown work very nicely.
- pjm331 3y ago
  I have the exact same system but step 4 is eMacs org mode However my script only opens up the current date - love your extension to enable opening up other dates - gonna steal that :)
- JenrHywy 3y ago
  I do something similar, but switched from bash/vim/markdown to Joplin a while back. I lost the immediacy of bash, but seamless syncing and editing across multiple devices, especially mobile, made it worth it. The main thing is that Joplin is still markdown, and I can trivially export if I want to switch to something else.
- runald 3y ago
  The code at https://jodavaho.io/posts/bash-journalling.html https://jodavaho.io/posts/bash-journalling.html doesn't work for me. It looks like it is passing vim the -d args, which doesn't seem right since -d opens a diff view. I think you misplaced a comma for the date command. I fixed it for me by doing like this: function journal() { vim $logdir/$(date +%Y-%m-%d -d "$\*") }
  - jvanderbot 3y ago
    Not a comma, but a close-paren. It turns out I had almost precisely that code in my bashrc (had below), so I updated the post to reflect this / your suggestion. function journal() { vim $logdir/$(date +%Y-%m-%d -d "$*").md } Thanks!
    - runald 3y ago
      Oh right, why did I say comma.

jvanderbot 3y ago

I agree. I suspect with some level of curmudgeonness that it's because author calls themself a pixel-artist. I have a brutalist CLI/programmer take on bullet journalling from vim, just for comparison: https://jodavaho.io/posts/bash-journalling.html https://jodavaho.io/posts/bash-journalling.html https://jodavaho.io/posts/bullet-journalling.html https://jodavaho.io/posts/bullet-journalling.html It is essentially: - One hidden folder for journal entries - Each entry is a file of the form YYYY-MM-DD.md - A bash alias will open today's file (or "yesterday" or "next thursday" or "2 weeks") using the date cli util - A few vim formatting steps make the already-well-functioning github markdown work very nicely.

pjm331 3y ago
I have the exact same system but step 4 is eMacs org mode However my script only opens up the current date - love your extension to enable opening up other dates - gonna steal that :)
JenrHywy 3y ago
I do something similar, but switched from bash/vim/markdown to Joplin a while back. I lost the immediacy of bash, but seamless syncing and editing across multiple devices, especially mobile, made it worth it. The main thing is that Joplin is still markdown, and I can trivially export if I want to switch to something else.
runald 3y ago
The code at https://jodavaho.io/posts/bash-journalling.html https://jodavaho.io/posts/bash-journalling.html doesn't work for me. It looks like it is passing vim the -d args, which doesn't seem right since -d opens a diff view. I think you misplaced a comma for the date command. I fixed it for me by doing like this: function journal() { vim $logdir/$(date +%Y-%m-%d -d "$\*") }
- jvanderbot 3y ago
  Not a comma, but a close-paren. It turns out I had almost precisely that code in my bashrc (had below), so I updated the post to reflect this / your suggestion. function journal() { vim $logdir/$(date +%Y-%m-%d -d "$*").md } Thanks!
  - runald 3y ago
    Oh right, why did I say comma.