Markwhen

Appearance

I need help with this

Timezones ​

Oh man, I don't like timezones

— Rob Koch, Markwhen creator and maintainer

We can (and should) specify a timezone for our markwhen documents by adding a timezone or tz header entry and similar for events:

mw
---
timezone: America/New_York
 
#covid: blue
#london:
  color: green
---
 
2020: Mostly uneventful year #covid
 
group year abroad #london
  2023-06-01: the king was coronated
    timezone: Europe/London
  ...
endGroup

This way, any event that isn't otherwise explicitly given a zone, like 2023-06-01: the king was coronated is, will be in the America/New_York zone.

Time zones can be specified by their name, like America/Los_Angeles, or by a offset, like +5 or -3.

Luxon

Much of markwhen's parsing, including timezone parsing, is done with Luxon. Read more about timezones on luxon's documentation

When to specify a timezone

The general advice is you should always specify a timezone - less ambiguity is better. Otherwise, you should specify a timezone if or when you start to use markwhen for things like calendaring or keeping track of responsibilities, where your events are measured in hours and minutes instead of days, months, and years.

Different start and end zones ​

If your start and end ranges for an event are different, separate out the zones with from and to:

mw
2025-06-09 11am / 2025-06-09 6:40pm: 🛫 Going home to NYC from LA
  timezone: 
    from: America/Los_Angeles
    to: America/New_York