mhc(5)

πŸ¦‹ mhc β€” Message Harmonized Calendaring system πŸ’–

okay so this is the mhc(5) page, it lives in the File Formats Manual section, and bestie, it's a whole vibe. Let's get into it.


✨ NAME ✨

mhc β€” the Message Harmonized Calendaring system. that's it, that's the name, iconic.


🌸 DESCRIPTION 🌸

So this page is the quick lil rundown of the mhc file format, fr fr. And a heads up: this manual page was written for the Debian GNU/Linux distribution, specifically because the original program does not have a manual page. not me having to write the docs myself πŸ’€ anyway.


πŸŽ€ FIELDS πŸŽ€

The mhc file format is based on STD11/RFC822: Standard for the format of ARPA Internet text messages. And in an mhc file, the following extra header fields get used. slay.

  • X-SC-Day: β€” the date of the event, formatted as yyyymmdd. You can put multiple dates in here, separated by spaces, like this:
X-SC-Day: 19990409 19990413

which means April 9th 1999 and April 13th 1999. two for one, we love to see it 🫢

  • X-SC-Time: β€” the time of the event, formatted as hh:mm-hh:mm or just hh:mm. If the event has no meaning attached to its time, you can just leave this field empty. no pressure.
  • X-SC-Duration: β€” the period of the event, formatted as yyyymmdd-yyyymmdd. You're allowed to omit the start date or the end date, like "19991121-". Important bestie: X-SC-Duration: is used only to limit the date specified by X-SC-Day: or X-SC-Cond, so you can't describe an event date using only X-SC-Duration:. If X-SC-Duration: is empty, that means no limit.
  • X-SC-Cond: β€” the condition of the event date, using the following keywords:
    • 00-31 β€” day of month.
    • 1st 2nd 3rd 4th 5th Last β€” week in month.
    • Sun Mon ... Sat β€” day of week.
    • Jan Feb ... Dec β€” month.

and here are the examples, because examples are the moment:

X-SC-Cond: Tue Fri

every Tuesday and Friday.

X-SC-Cond: 31 Aug

every August 31th.

X-SC-Cond: 1st 3rd Fri

every 1st and 3rd Friday.

X-SC-Cond: Fri
X-SC-Day: !19990409

every Friday, but except April 9th 1999.

X-SC-Cond: Fri 13

every 13th and every Friday, not 13th Friday. (yes, that distinction is the whole point, pay attention πŸ’…)

  • X-SC-Alarm: β€” a hint for the alarm of the event. Currently mhc.el doesn't alarm, but gemcal will pop-up an alarm window. It'll be useful if you transfer this event to PalmOS. In X-SC-Alarm:, you can specify a number (1 to 99) with a suffix like minute, hour or day. For example:
X-SC-Alarm: 10 minutes

alarm 10 minutes before the event.

X-SC-Alarm: 3 hour

alarm 3 hours before the event.

X-SC-Alarm: 3 day

alarm 3 day before the event.

  • X-SC-Subject: β€” subject of event. unstructured? 🀷
  • X-SC-Location: β€” location of event. unstructured? 🀷
  • X-SC-Category: β€” category of event. Any keyword, space separated. Case ignored. For example:
X-SC-Category:
X-SC-Category: todo
X-SC-Category: done
X-SC-Category: private todo
X-SC-Category: work done
  • X-SC-Record-Id: β€” internal use only. don't touch it, it's not for you bestie πŸ™ˆ

πŸ”₯ SEE ALSO πŸ”₯

  • mhc(1). go read that one too, it's giving main character energy.

πŸ‘‘ AUTHOR πŸ‘‘

This program was written by Yoshinari Nomura <nom@quickhack.net>, and this manual page was written by Fumitoshi UKAI <ukai@debian.or.jp>, for the Debian GNU/Linux system (but may be used by others). legends, both of them, no cap.


and that's the whole page!! πŸ’œ it went out on 10 Jun 2015, and it's the mhc(5) page from the File Formats Manual β€” so if you ever forget the date, it's right there at the bottom, forever. periodt. βœ¨πŸŽ€πŸŒˆ