DATEDIFF(1)

🌸 datediff(1) 🌸

okay bestie, buckle up — this is the manual page for datediff, and it's literally about computing a duration from a DATE/TIME (the reference date/time) to the other date/time(s) you throw at it. group-chat energy only, but the facts stay exactly where they belong. 💅

---

💖 NAME 💖

datediff — compute duration from DATE/TIME (the reference date/time) to the other 💫

---

🦋 SYNOPSIS 🦋

datediff [OPTION]...  DATE/TIME [DATE/TIME]...

---

✨ DESCRIPTION ✨

So datediff computes the duration from DATE/TIME (that's the reference date/time, the main character) to the other DATE/TIMEs you give it, and then prints the result as a duration. If you don't give the other DATE/TIMEs, it reads them from stdin. no cap. 🫶

DATE/TIME can also be one of these specials:

• now — interpreted as the current (UTC) time stamp
• time — the time part of the current (UTC) time stamp
• today — the current date (according to UTC)
• tomo[rrow] — tomorrow's date (according to UTC)
• y[ester]day — yesterday's date (according to UTC)

💡 Note: the output format of durations (the one you set with -f) takes all the format specifiers into account. So if you specify %M and %S, for example, it prints the duration in minutes and seconds; if you specify %S only, it prints the duration in seconds. iykyk.

See section The refinement rule in ddiff(1).

---

🎀 OPTIONS 🎀

🌟 Recognized OPTIONs 🌟

• -h, --help — print help and exit. iconic behavior.
• -V, --version — print version and exit. slay.
• -q, --quiet — suppress the message about date/time and duration parser errors and fix-ups. The default is to print a warning or the fixed-up value and return error code 2. Also see -S/--skip-illegal to output an empty line instead of leaving out the line altogether. lowkey important.
• -S, --skip-illegal — deprecated, use -E/--empty-mode. 🚨 yes, deprecated, bestie, don't build your whole vibe on it.
• -E, --empty-mode — output empty lines as a placeholder for illegal input, i.e. parser errors or date/times that cannot be subtracted.
• -f, --format=STRING — output format. This can either be a specifier string (similar to strftime()'s FMT) or the name of a calendar. choose your fighter.
• -i, --input-format=STRING... — input format, can be used multiple times. Each date/time will be passed to the input format parsers in the order they are given; if a date/time can be read successfully with a given input format specifier string, that value will be used. order matters, periodt.
• -b, --base=DT — for underspecified input use DT as a fallback to fill in missing fields. Also used for ambiguous format specifiers to position their range on the absolute time line. Must be a date/time in ISO8601 format. If omitted, defaults to the current date/time.
• -e, --backslash-escapes — enable interpretation of backslash escapes in the output and input format specifier strings. fancy.
• --from-locale=LOCALE — interpret dates on stdin or the command line as coming from the locale LOCALE. This would only affect month and weekday names, as input formats have to be specified explicitly.
• --from-zone=ZONE — interpret dates on stdin or the command line as coming from the time zone ZONE. timezone queen behavior.

---

🌈 FORMAT SPECS 🌈

Format specs in dateutils are similar to posix' strftime(). cute.

However, due to a broader range of supported calendars, dateutils must employ different rules. it's giving "we had to switch it up." 💅

📅 Date specs

• %a — the abbreviated weekday name
• %A — the full weekday name
• %_a — the weekday name shortened to a single character (MTWRFAS)
• %b — the abbreviated month name
• %B — the full month name
• %_b — the month name shortened to a single character (FGHJKMNQUVXZ)
• %c — the count of the weekday within the month (range 00 to 05)
• %C — the count of the weekday within the year (range 00 to 53)
• %d — the day of the month, 2 digits (range 00 to 31)
• %D — the day of the year, 3 digits (range 000 to 366)
• %F — equivalent to %Y-%m-%d (ymd's canonical format)
• %g — ISO week date year without the century (range 00 to 99)
• %G — ISO week date year including the century
• %j — equivalent to %D
• %m — the month in the current calendar (range 00 to 12)
• %Q — the quarter of the year (range Q1 to Q4)
• %q — the number of the quarter (range 01 to 04)
• %s — the number of seconds since the Epoch.
• %u — the weekday as number (range 01 to 07, Sunday being 07)
• %U — the week count, day of week is Sun (range 00 to 53)
• %V — the ISO week count, day of week is Mon (range 01 to 53)
• %w — the weekday as number (range 00 to 06, Sunday being 00)
• %W — the week count, day of week is Mon (range 00 to 53)
• %y — the year without a century (range 00 to 99)
• %Y — the year including the century
• %_y — the year shortened to a single digit
• %Z — the zone offset in hours and minutes (HH:MM) with a preceding sign (+ for offsets east of UTC, - for offsets west of UTC)

also these roman-numeral cuties:

• %Od — the day as roman numerals
• %Om — the month as roman numerals
• %Oy — the two digit year as roman numerals
• %OY — the year including the century as roman numerals

and these calendar-specific ones:

• %rs — in time systems whose Epoch is different from the unix Epoch, this selects the number of seconds since then.
• %rY — in calendars with years that don't coincide with the Gregorian years, this selects the calendar's year.

ordinal girlies:

• %dth — the day of the month as an ordinal number, 1st, 2nd, 3rd, etc.
• %mth — the month of the year as an ordinal number, 1st, 2nd, 3rd, etc.

business-day behavior:

• %db — the business day of the month (since last month's ultimo)
• %dB — number of business days until this month's ultimo

⏰ Time specs

• %H — the hour of the day using a 24h clock, 2 digits (range 00 to 23)
• %I — the hour of the day using a 12h clock, 2 digits (range 01 to 12)
• %M — the minute (range 00 to 59)
• %N — the nanoseconds (range 000000000 to 999999999)
• %p — the string AM or PM, noon is PM and midnight is AM.
• %P — like %p but in lowercase
• %S — the seconds (range 00 to 60, and 60 is for leap seconds)
• %T — equivalent to %H:%M:%S

🧚 General specs

• %n — a newline character
• %t — a tab character
• %% — a literal % character

💅 Modifiers

• %O — modifier to turn decimal numbers into Roman numerals
• %r — modifier to turn units into real units
• %0 — modifier to turn on zero prefixes
• %SPC — modifier to turn on space prefixes
• %- — modifier to turn off prefixes altogether
• th — suffix, read and print ordinal numbers
• b — suffix, treat days as business days

🚨 By design dates before 1601-01-01 are not supported. like, not even a little bit.

For conformity, here is a list of calendar designators and their corresponding format string:

• ymd — %Y-%m-%d
• ymcw — %Y-%m-%c-%w
• ywd — %rY-W%V-%u
• bizda — %Y-%m-%db
• lilian — n/a
• ldn — n/a
• julian — n/a
• jdn — n/a
• matlab — n/a
• mdn — n/a

These designators can be used as output format string, and moreover, @code{lilian}/@code{ldn} and @code{julian}/@code{jdn} can also be used as input format string.

---

🍓 FORMAT SPECS FOR DURATIONS 🍓

Unlike time or absolute instants, durations are reference-free, i.e. the reference instant is not part of the duration. As a result, durations cannot be named, i.e. there is no naming scheme that applies to all durations and all references unambiguously. it's giving "no labels, just vibes." 😭

Consequently, none of the format specifiers for date/times makes sense for durations in the literal sense. However, to aid intuitive usage, we reused format specifiers when they represent integral values and a valid unit for duration, as follows:

📅 Date specs

• %c — equivalent to %w
• %d — duration in days
• %F — equivalent to %dd with no resorting to bigger units
• %m — duration in months
• %w — duration in weeks
• %y — equivalent to %Y
• %Y — duration in years
• %db — duration in business days
• %dB — equivalent to %db

⏰ Time specs

• %H — duration in hours
• %I — equivalent to %H
• %M — duration in minutes
• %S — duration in seconds
• %T — equivalent to %Ss without resorting to bigger units
• %rS — duration in real-life seconds, as in including leap seconds
• %rT — equivalent to %rSs without resorting to bigger units

🧚 General specs

• %n — a newline character
• %t — a tab character
• %% — a literal % character

💅 Modifiers

• %r — modifier to turn units into real units
• %0 — modifier to pad refined values with zeroes
• %SPC — modifier to pad refined values with spaces
• b — suffix, treat days as business days

---

👑 THE REFINEMENT RULE 👑

Durations are somewhat ambiguous when it comes to representing them through format specifiers. Unlike format specifiers in point-in-time representations, duration specifiers can have an intra-line relationship. messy, but we move. 💅

So for instance, a duration of 128 seconds might be presented through "%S" as "128" but similarly through "%M:%S" as "02:08" (read two minutes and 8 seconds). see? cute.

There are several approaches to dealing with this ambiguity. The ddiff tool will follow what we call the refinement rule. That is, regardless of the position of a format specifier, if it is a valid refinement of another specifier in the format string, then it will only show the fractional value, i.e. the value in its natural range with respect to the refined specifier. no cap.

• %Y — possible refinements: %m, %w, %d
• %m — possible refinements: %w, %d
• %w — possible refinements: %d
• %d — possible refinements: %H, %M, %S
• %H — possible refinements: %M, %S
• %M — possible refinements: %S

The refinement alternatives are listed in order of precedence and they are mutually exclusive. I.e. it is not possible to express a duration in months and hours without having a "%d" specifier as well. On the other hand, in a chain of refinements, inner elements are optional, i.e. you can express a duration in weeks and hours because every day has 24 hours and hence there are 168 hours in a week. math ate. 🔥

In case of negative durations (the minuend is in the future relative to the subtrahend), only the largest unit will carry the minus sign.

Using the refinement rule keeps the format string dead simple — there's no need for operators or a full-blown language to distinguish the range ambiguity, which then would have to be escaped because they could also in theory be part of the literal characters of the format string. That whole mess results more often than not in command lines that are hard to craft and even harder to understand later on (e.g. if used in shell scripts). literally the worst.

The refinement rule ingeniously covers the 99% case but, unlike other approaches, there's no way to display two unrefined values in the same format string, e.g. "'%w weeks (which is %d days)'". 🙈

✨ EXAMPLES ✨

okay bestie this is the fun part — real commands, real outputs, no cap 💅 every single one is here, exactly as it'll look in your terminal 🫶

Same day? Zero. Obviously. ✨

$ ddiff 2012-03-02 2012-03-02
0
$

Ten days apart in March 🎀

$ ddiff 2012-03-02 2012-03-12
10
$

Crossing into April, so it's 41 days 👑

$ ddiff 2012-03-02 2012-04-12
41
$

March 12 → April 2, that's 21 🌸

$ ddiff 2012-03-12 2012-04-02
21
$

Flip the order and it just goes negative, she's consistent like that 😭

$ ddiff 2012-04-02 2012-03-12
-21
$

Now with a format spec — %dd gives you days with a cute little d glued on 💖

$ ddiff 2012-01-02 2012-02-29 -f '%dd'
58d
$

Stack two specs and you get weeks and days, iconic combo ✨

$ ddiff 2012-01-02 2012-02-29 -f '%ww %dd'
8w 2d
$

Times work too, same energy 🕐

$ ddiff 10:00:00 10:00:00
0s
$

$ ddiff 10:01:00 10:06:00
300s
$

$ ddiff 10:06:00 10:01:00
-300s
$

%S = seconds, and yes you can put literal words around it 🔥

$ ddiff 10:01:00 11:03:10 -f '%S sec'
3730 sec
$

Minutes and seconds together, slay 🎀

$ ddiff 10:01:00 11:03:10 -f '%Mm %Ss'
62m 10s
$

Classic %H:%M:%S giving clock vibes — and notice there's no zero-padding, so it's 1:2:10 not 01:02:10, lowkey a whole look 💀

$ ddiff 10:01:00 11:03:10 -f '%H:%M:%S'
1:2:10
$

Full timestamps? Yeah she eats those for breakfast 👑

$ ddiff 2012-03-02T10:04:00 2012-03-02T10:14:00
600s
$

$ ddiff 2012-03-02T10:04:00 2012-03-02T10:14:00 -f '%M min'
10 min
$

Big ol' gap across two days 🦋

$ ddiff 2012-03-01T12:17:00 2012-03-02T14:00:00
92580s
$

And the same gap dressed up all fancy — mixing days and seconds in one format string, main character energy fr fr 💜

$ ddiff 2012-03-01T12:17:00 2012-03-02T14:00:00 -f '%d days and %S seconds'
1 days and 6180 seconds
$

---

🌈 AUTHOR 🌈

Written by Sebastian Freundt <freundt@fresse.org> — king behavior, we stan 💖

---

🙈 REPORTING BUGS 🙈

Found a bug? Report it, bestie, don't just suffer in silence 😭

Report bugs to: https://github.com/hroptatyr/dateutils/issues

---

👑 SEE ALSO 👑

The full documentation for datediff is maintained as a Texinfo manual 📚 if the info and datediff programs are properly installed at your site, this command

info (dateutils)datediff

should give you access to the complete manual ✨ go read it, it's giving thorough 🫶

---

okay that's the whole page bestie, you're officially a datediff expert 💅✨

this beauty's from dateutils 0.4.11, dated January 2024, and it's page DATEDIFF(1) — go forth and diff some dates 🎀💖