- Use their calendars all the time for various planning or visualizations. Like before exams I used to print one out, mark each exam, and work backward which days I would study for which subject.
- The astronomy stuff is super useful. https://www.timeanddate.com/astronomy/night/ and it runs great on a phone. Aka I can be outside and use this page to know exactly what I'm looking at in the sky, or use it to plan to see what will be visible tonight.
- I have a simple timer counting down to our planned vacation. Just fun to go to the tab and daydream.
- When various holidays or red days are. Especially those that move and aren't normally marked on a calendar. Like when this and that part of Norway has their winter break.
It‘s weird in general how tools/ websites seem to avoid putting too much information on a screen (see also: event listings, …). Why is that? Most people have big screens nowadays, so it would be feasible to have a view like the one described here, at least for desktop calendars.
[0] https://www.calendarpedia.co.uk/download/calendar-2025-portr...
For a long time, I just had some "future log" pages (actually I tend to have 3-4 years worth) at the start of each book, where I have 3 months per page so I can drop in important future events (like booking a holiday 12 months out), birthdays etc (although I only copy these forward annually) and then a "month ahead" page at the start of each page where I had a line per day. I found that I wasn't really using most of these lines though because mostly only the weekends were useful for me.
I switched to having a 9 month-view where I have a line per week, and the left page is the weekend and the right page for weekdays. I pen in the dates for every weekend day, and tend to only fill in the dates on the weekdays when I have something to add on a specific day. I only ever write in pencil on these pages apart from the dates in pen, so blocks can be erased easily, and I tend to use corner square brackets to highlight start and ends of longer special periods like holidays. It's a bit annoying not having a full 12-month view, but I also like the fact that because it starts at some key event, then it usually crosses the year boundary. I tend to use these as future planning rather than recording events, and if it gets messy with too much rubbing out or crossing out, then I'll just start a new one from current (or occasionally a couple of weeks back) and put a note on the old page linking to the page number with the new calendar, and a note on the new one linking to the last.
Quite interesting how people are so different.
Any app I find seems to disappear from the Play Store after a couple years.
Bonus: show the weeks vertically.
Source: bsdmainutils
Maintainer: Debian Bsdmainutils Team
[...]
Description-en: display a calendar and the date of Easter
[...] This utility displays a
simple calendar in a traditional or an alternative and more advanced layout,
and the date of Easter.
3 months per row (so 4 rows).
Within each month the weeks should be shown vertically (this was common when I was a kid, now even a google image search for yearly calendar shows only horizontal weeks).
Hate to say it but you can just tell an LLM to make the calendar for you as an html artifact that includes a print view. It can also add a .ics export.
Of course you should go over the dates and holidays to see if it got them right.
https://world.hey.com/michelleharjani/building-hey-calendar-...
It has all you want, plus moon phases!
It's admittedly harder to find these days, and someone should rewrite it in a decent language, but here it is:
> someone should rewrite it in a decent language
was coded in BAGS (bash, awk, grep, sed) and Postscript circa 1987 [1], and it's still working almost 40 years later in 2026 !
Perhaps it was in fact coded decently. And licensed decently as well. ^_^
[1]
AUTHOR:
Patrick Wood
Copyright (C) 1987 by Pipeline Associates, Inc.
Permission is granted to modify and distribute this free of charge.It’s hard to maintain though unless you really know your BAGS well.
Before vibe coding, I had tried to rewrite it in python, I believe, and it turned out not to be easier to read at all… but then I got sidetracked and put the project aside.
In my defense, pcal is a rewrite in c and seems horribly complex in comparison.
Maybe I should try to finish it. I hope Pat Wood won’t mind.
Probably a bit overkill, since the locations only "overlap" one day max, but I like the clear spacing.