Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Calendar.txt

terokarvinen.com

Post reply on HN
Print view View original

71–80 of 143 posts

Re: Calendar.txt

#71

Post by s0fasurfa »

Nice idea, but the calendar format is a bit verbose for my taste. Week number is something I would have to look up constantly and surely get wrong more than once.

If you want to follow UNIX philosophy, why don't you write an augmenter/converter tool `caug` that adds "computed" information such as week number, weekday or even relative date?

  > cat calendar-src.txt

    2025
    ====
    03-01 9-12 project groups

  > cat calendar-src.txt | caug
    2025-03-01 w09 09:00-12:00 project groups +tomorrow 
    +thisweek

  > cat calendar-src.txt | caug | grep "thisweek"
    2025-03-01 w09 09:00-12:00 project groups +tomorrow 
    +thisweek

Re: Calendar.txt

#73

Post by tero »

s0fasurfa wrote: post #71

Nice idea, but the calendar format is a bit verbose for my taste. Week number is something I would have to look up constantly and surely get wrong more than once. If you want to follow UNIX philosophy, why don't you write an augmenter/converter tool `caug` that adds "computed" information such as week number, weekday or even relative date? > cat calendar-src.txt 2025 ==== 03-01 9-12 project groups > cat calendar-src.…

I use a template [1] that includes week numbers.

With some traditional GUI calendar software, I was often hunting and miscopying week numbers. Some software also had a weird (non ISO-8601) idea of week numbers.

In case you need calendar.txt after 2033, I wrote a small tool [2] to generate more templates.

[1] https://terokarvinen.com/2021/calendar-txt/calendar-txt-unti...

[2] https://terokarvinen.com/2021/calendar-txt/calendartxt-gener...

Re: Calendar.txt

#74

Post by danso »

s0fasurfa wrote: post #71

Nice idea, but the calendar format is a bit verbose for my taste. Week number is something I would have to look up constantly and surely get wrong more than once. If you want to follow UNIX philosophy, why don't you write an augmenter/converter tool `caug` that adds "computed" information such as week number, weekday or even relative date? > cat calendar-src.txt 2025 ==== 03-01 9-12 project groups > cat calendar-src.…

That was my first thought too; I often use Google Sheets/Excel as a lightweight todo calendar, and I'll make formulas to calculate week-of-year and day-of-week. These lists are so lightweight and adhoc that having to do that kind of calculation would be enough friction to not maintain the lists after a short period

Re: Calendar.txt

#75

Post by abound »

tero wrote: post #55
Communitivity wrote: post #52

I like this, but need more detail in my log and have too many things in a given day to have them all on a line. Had the following idea, and will try it out at some point. Call it calendar.md Use calendar.txt format and method with the following changes: 1) Use markdown, with a top level heading of Calendar (so inclusion is easier) and the portion 2) Use :tag: instead of +tag. Tags can be run together (:tag:tag2:). Th…

I especially like your 'mgrep', please do write it! I have considered similar tools that make use of MarkDown syntax, I feel that there are many tools waiting to be written here.

I think mdq [1], which was recently on HN somewhere, fits this.

[1] https://github.com/yshavit/mdq

Re: Calendar.txt

#76

Post by tero »

abound wrote: post #75
tero wrote: post #55

Earlier quoted context omitted.

I especially like your 'mgrep', please do write it! I have considered similar tools that make use of MarkDown syntax, I feel that there are many tools waiting to be written here.

I think mdq [1], which was recently on HN somewhere, fits this. [1] https://github.com/yshavit/mdq

Mdq seems just what I've been looking for. I have yet to test it.

Based on documentation, you can mdq for the chapter whose heading is "## Foobar"; or extract all lists in chapter "### Xyzzy".

Thanks, abound!

Update: mdq discussion https://news.ycombinator.com/item?id=43152704

Re: Calendar.txt

#77

Post by kragen »

I've been doing this since 02001, except without the week numbers. I switched from CVS to Git around 02009.

Anyone who knows me will tell you I am not very organized. Possibly this is why.

Android support is definitely substandard, even with Termux.

It's not foolproof. On one occasion I typed in the month wrong, though in the right place in the file. When I noticed that the line was out of order, I moved it to where the date said it should be. Arriving a month late, I discovered that the studio space I'd paid for no longer existed.

Re: Calendar.txt

#78

Post by Spare_account »

kragen wrote: post #77

I've been doing this since 02001, except without the week numbers. I switched from CVS to Git around 02009. Anyone who knows me will tell you I am not very organized. Possibly this is why. Android support is definitely substandard, even with Termux. It's not foolproof. On one occasion I typed in the month wrong, though in the right place in the file. When I noticed that the line was out of order, I moved it to where…

I like your future proof year numbering. Most current date formats are going to have a BIIG problem come the end of 9999 but not you!

Re: Calendar.txt

#79

Post by jrm4 »

In the spirit of friendly competition; I gotta argue that Skroll's "Remind" supercedes this in every way. More flexible and more powerful.

Re: Calendar.txt

#80

Post by vhantz »

guessmyname wrote: post #8

I created a super-simple CalDav-esque web endpoint in my personal website that receives HTTP requests from a command line tool, stores the calendar events, and then returns them as a dynamic ICS file. Then, I use Apple’s Calendar app to subscribe to a “hidden” URL and iCloud automatically distributes the subscription to all my devices. It sounds super dumb but it works so well. The main feature is that I can categori…

Could you elaborate on the "hidden URL"?
Post reply on HN