|CALENDAR(1)||General Commands Manual||CALENDAR(1)|
calendarutility checks the current directory or the directory specified by the
CALENDAR_DIRenvironment variable for a file named calendar and displays lines that begin with either today's date or tomorrow's. On Fridays, events on Friday through Monday are displayed.
The options are as follows:
To handle calendars in your national code table you can specify “LANG=<locale_name>” in the calendar file as early as possible. To handle national Easter names in the calendars, “Easter=<national_name>” (for Catholic Easter) or “Paskha=<national_name>” (for Orthodox Easter) can be used.
The “CALENDAR” variable can be used to specify the style. Only ‘Julian’ and ‘Gregorian’ styles are currently supported. Use “CALENDAR=” to return to the default (Gregorian).
To enforce special date calculation mode for Cyrillic calendars you should specify “LANG=<local_name>” and “BODUN=<bodun_prefix>” where <local_name> can be ru_RU.UTF-8, uk_UA.UTF-8 or by_BY.UTF-8.
Other lines should begin with a month and day. They may be entered
in almost any format, either numeric or as character strings. If proper
locale is set, national months and weekdays names can be used. A single
asterisk (‘*’) matches every month. A day without a month
matches that day of every week. A month without a day matches the first of
that month. Two numbers default to the month followed by the day. Lines with
leading tabs default to the last entered date, allowing multiple line
specifications for a single date. “Easter” (may be followed by
a positive or negative integer) is Easter for this year.
“Paskha” (may be followed by a positive or negative integer)
is Orthodox Easter for this year. Weekdays may be followed by
... “+5” (aliases
last, first, second, third, fourth) for moving events like “the last
Monday in April”.
By convention, dates followed by an asterisk (‘*’) are not fixed, i.e., change from year to year.
Day descriptions start after the first <tab> character in the line; if the line does not contain a <tab> character, it isn't printed out. If the first character in the line is a <tab> character, it is treated as the continuation of the previous description.
The calendar file is preprocessed by
cpp(1), allowing the inclusion of shared
files such as company holidays or meetings. If the shared file is not
referenced by a full pathname, cpp(1)
searches in the current (or home) directory first, and then in the directory
/usr/share/calendar. Empty lines and lines protected
by the C commenting syntax (
/* ... */) are
Some possible calendar entries (a \t sequence denotes a <tab> character):
LANG=C Easter=Ostern #include <calendar.usholiday> #include <calendar.birthday> 6/15\tJune 15 (if ambiguous, will default to month/day). Jun. 15\tJune 15. 15 June\tJune 15. Thursday\tEvery Thursday. June\tEvery June 1st. 15 *\t15th of every month. May Sun+2\tsecond Sunday in May (Muttertag) 04/SunLast\tlast Sunday in April, \tsummer time in Europe Easter\tEaster Ostern-2\tGood Friday (2 days before Easter) Paskha\tOrthodox Easter
calendarchanges into, if it exists).
calendarwill not send mail if this file exists.
calendarprogram previously selected lines which had the correct date anywhere in the line. This is no longer true: the date is only recognized when it occurs at the beginning of a line.
calendarcommand appeared in Version 7 AT&T UNIX.
calendardoesn't handle all Jewish holidays or moon phases.
|January 29, 2019||OpenBSD-current|