I'm the creator of Calendar.txt. I'm very happy to see this on Hacker News.
I've used Calendar.txt as my calendar for over a year (and previous versions before that). Having previously marketed both digital and paper calendars, and tested the digital variety, I felt they were excessively complicated.
For me, the benefits of calendar.txt have been reliability, simplicity and integration with established Linux tooling (grep, git, scripts). The downside has been lack of automatic synchronization, a tradeoff for simplicity and reliability.
If you want to ask about using Calendar.txt, I'll check here during breaks from my Django intensive course.
I've decided to use your text file template the other way round: one line at the end of each day about what I did. Sort of a personal log. Thanks for nudging me into that direction.
My teacher voice says: concentrate on your Django course while you can bombard the facilitator and participants with questions.
Hi colleague, I'm teaching the course, so the students are asking the questions.
Happy to hear that you've found a new use, journaling, for calendar.txt. I'm using it similarly myself, even though it's not mentioned on the page. For some projects, I collect billable hours from old calendar.txt entries ('grep +theproject calendar.txt'). I also use it to record some results, e.g. Cooper x meters on this date.
Do you use calendar.txt for journaling and another program for calendar planning? If so, what are you using for a calendar?
Well now I wonder why I assumed that you were a participant? I've got some thinking to do about that one!
I plan to rename my copy of calendar.txt to yesterday.txt. Each morning my plan is to write something about what I did yesterday with a view to extracting themes - perhaps like not making assumptions about the roles people on forums might have. I'm thinking some code words might emerge like '$ScreenTime 3'. But I'll see.
Planning: I am actually a teacher in adult education so we operate on pre-determined timetables for each class. I have a document called a 'scheme of work' which I use to plan what happens each week in a given class with space for a bit of a note after each session about what actually happened. Schemes of work are 'working documents' - they change as the year unfolds. My life in general just lives on a (paper) calendar on the notice board in the kitchen.
And I am writing my dissertation, so technically, those stats & the guess are also correct.
2b3a51, interesting planning process. My system with calendar.txt and planning courses: I use week headings for marking the periods and period weeks (4p1). When reserving course days, I just put the tags there (+pw). Later, when I decide the main theme, I add it ("+pw deploy"). If there is a special channel, guests and other info, I add it as it arrives.
For past events, calendar forms a nice basis. At least for me, most of the stuff I plan, happens. I understand you add some insight there, maybe I should try that, too.
I wrote something similar ~5 years ago, as a reminder mechanism for myself (never shared it, it's very basic).
calendar.txt (lowercase for my filename) but only 'YYYYMMDD thing' for how the content line was - you've got more structure going on so that's cool, I like the week numbering - good idea.
calendar.sh was my little grep reminder tool running from cron.
I'm the creator of Calendar.txt. I'm very happy to see this on Hacker News.
I've used Calendar.txt as my calendar for over a year (and previous versions before that). Having previously marketed both digital and paper calendars, and tested the digital variety, I felt they were excessively complicated.
For me, the benefits of calendar.txt have been reliability, simplicity and integration with established Linux tooling (grep, git, scripts). The downside has been lack of automatic synchronization, a tradeoff for simplicity and reliability.
If you want to ask about using Calendar.txt, I'll check here during breaks from my Django intensive course.