Site Map - skip to main content - dyslexic font - mobile - text - print

Hobby Public Radio

Your ideas, projects, opinions - podcasted.

New episodes Monday through Friday.

Please support our Patrons

Our hosting is kindly provided by Josh from We would appreciate it if you could donate to help reduce his costs in funding the hosting. He is also accepting bitcoins to 1KsxJr9HtsdaUeU7yaV9bk9bQi21UPBtUq
Please also consider supporting the who are now hosting our media files. Right now, a generous supporter will match your contributions 3-to-1. So your $5 donation results in $20 for the Internet Archive.

hpr2145 :: Daily notes and todo list with markdown

How I use markdown and git to keep up with what I do

<< First, < Previous, Latest >>

Hosted by norrist on 2016-10-21 is flagged as Clean and is released under a CC-BY-SA license.
Listen in ogg, spx, or mp3 format. | Comments (6)

Using Markdown and git to store your todo list and daily journal

Why markdown
  • No distractions
  • Simple syntax
  • Plain text, Human readable.
  • Inline HTML
  • Easy conversion to other formats
Why git
  • Any SCM probably OK
  • Github and Gitlab render markdown.
The todo page
    # TODO

    ### Can do now
    * Bullet 1
    * Bullet 2

    ### Near term
    1. Numbered 1
    1. Numbered 2

    ### Long term
The journal script
    DAILYFILE="/Users/norrist/Projects/todo/daily/$(/bin/date +%F).md"

    if [ -f $LOCKFILE ]
            echo "$LOCKFILE PRESENT - ABORTING"
            read -n1 -p "Remove and Continue? [y,n]" doit
                case $doit in
                    y|Y) echo "Continuing with $LOCKFILE PRESENT" ;;
                    *) exit 1 ;;

            echo "NO LOKCFILE"
            touch $LOCKFILE


    if [ -f $DAILYFILE ]
            echo "$DAILYFILE exists"
            echo  >> $DAILYFILE
            echo  "-----">> $DAILYFILE
            echo "# $(/bin/date +%F)" >> $DAILYFILE
            echo  >> $DAILYFILE
            echo "### Projects" >> $DAILYFILE
            echo  >> $DAILYFILE
            echo "### Tickets" >> $DAILYFILE
            echo  >> $DAILYFILE
            echo "### Walkups" >> $DAILYFILE

    /usr/local/bin/edit -w --new-window $DAILYFILE
    /opt/local/bin/aspell -c $DAILYFILE
    /opt/local/bin/aspell -c $TODOFILE

    rm $LOCKFILE
    rm $DAILYPATH/


    for f in $(ls  -r $DAILYPATH/2*md)
     do cat $f >> $DAILYPATH/
     echo >>$DAILYPATH/

    cd /Users/norrist/Projects/todo; /usr/bin/git add . && /usr/bin/git commit -m "$(date)" && /usr/bin/git push origin master

Daily file template

    # 2016-08-02


    ### Projects

    ### Tickets

    ### Walkups
aspell is awesome


Subscribe to the comments RSS feed.

Comment #1 posted on 2016-10-21T06:05:01Z by b-yeezi

Love this Idea

Thanks for this show. I agree with your reasons for using markdown. It gets out of your way so you can write. I also find the idea of using git interesting, but I would be concerned about privacy. I guess you can host your own gitlab...

Can't wait for your next show.

Comment #2 posted on 2016-10-24T15:07:12Z by Fin

Nice! Licence?

Nice show! Sweet script! Is it up on a public git repo somewhere?

TL;DR Would you mind adding a licence?

You might think of it as just a little, personal convenience script that doesn't mean much, that anyone can adapt if they please right? But, technically speaking, you've got the copyright (by default) and I can't legally use this code.

You may consider it open source by being on a web page that is covered by the CC-BY-SA licence but they advise against it's use for software as it doesn't explicitly cover distribution of source code (see

I ask you to consider adding a licence to make it clear what people can do with your script. I'd sure love to use it but, if I make changes and want to share it, we're in a grey area ;)

Comment #3 posted on 2016-10-25T23:04:41Z by norrist

Version with copyright notice

Thanks for the feedback. Here is a link to the script with an ISC license header.

Comment #4 posted on 2016-11-30T20:47:38Z by Matt

question about the script

I love your script idea and will probably be copying lots of it. THANKS!

however, in the last "for" loop where you cat your files into the new "README" file, i don't understand this bit:

$(ls -r $DAILYPATH/2*md)

more specifically, the "2*/md" bit. Is this some kind of BASH specific notation? Is this a Mac thing?

OTW, great episode and very helpful!


Comment #5 posted on 2016-12-01T16:58:29Z by norrist


There isnt anything special about "2*/md". All the files that I want combined into the readme are named by date and have the md suffix. so "2*/md" matches as well as all the other daily files. The only reason for "2*/md" to be there is incase I have some other files in the directory that I dont want included in the readme.

Comment #6 posted on 2016-12-04T00:08:05Z by Matt

of course!

thanks... i wasn't thinking about dates starting with 2... duh


<< First, < Previous, Latest >>

Leave Comment

Note to Verbose Commenters
If you can't fit everything you want to say in the comment below then you really should record a response show instead.

Note to Spammers
All comments are moderated. All links are checked by humans. We strip out all html. Feel free to
record a show about yourself, or your industry, or any other topic we may find interesting. We also check shows for spam :).

Provide feedback
Your Name/Handle:
Anti Spam Question: What does the P in HPR stand for ?
Are you a spammer →
Who hosted this show →
What does HPR mean to you ?