DATEROUND(1)

πŸ“¦
version 0.4.11 Β· 5 versions
, in alpine 3.24, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

πŸ’– DATEROUND(1) πŸ’–

okay bestie, sit down, hydrate, and let me tell you about dateround β€” a User Commands era icon from the dateutils fam πŸ’…


✨ NAME ✨

dateround β€” round DATE/TIME to the next occurrence of RNDSPEC. that's the whole job, she's focused, she's booked, she's slaying πŸŽ€


🌸 SYNOPSIS 🌸

dateround [OPTION]...  [DATE/TIME] RNDSPEC...

πŸ¦‹ DESCRIPTION πŸ¦‹

Round DATE/TIME to the next occurrence of RNDSPEC. yes literally that. round it. to the next one. πŸ’«

If DATE/TIME is omitted a stream of date/times is read from stdin. no date? no problem, she'll just read them off the stream like a group chat πŸ™ˆ

DATE/TIME can also be one of the following 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)

  1. RNDSPECs can be month names (Jan, Feb, ...), weekday names (Sun, Mon, ...), numerals suffixed with y, q, mo, d, bd, h, m, or s, possibly prefixed with a dash (-) to indicate the rounding direction is downwards.
  2. Suffixed RNDSPECs may additionally be prefixed with a slash (/) to indicate that rounding to a multiple of RNDSPEC is desired. Co-class rounding.

In the first case, rounding affects the named element in the specified date or date/time and more significant elements by setting this element to the specified value and adjusting the more significant elements such that the result is greater (younger) or equal to the input (or strictly greater when -n|--next is given) for positive values, and less (older) or equal (unless -n|--next is given) for named elements that are prefixed with dash (-). In either case, less significant elements, e.g. subdivisions of the named element and their subdivisions are left unchanged.

That is     dateround 2019-01-28T12:04:00 +6
will yield  2019-02-06T12:04:00
Similarly   dateround -n 2019-01-28T12:04:00 -- -Oct
will yield  2018-10-28T12:04:00

In the second case, rounding is more like rounding decimal fractions to negative infinity. The time axis is partitioned by multiples of the named element, and the oldest date or datetime is returned that is greater (younger) (or equal if -n|--next is omitted) than the specified date or date/time, when rounding down (- prefix) the oldest date or datetime is returned that is less (older) than the specified date or datetime. πŸŒ€

That is     dateround 2019-01-28T12:04:00 /1y
will yield  2020-01-01T00:00:00
Similarly   dateround 2019-01-28T12:04:00 /-30m
will yield  2019-01-28T12:00:00

The superdivision of years are millennia, i.e. there's 1000 years, 500 biennia, 100 decades, etc. in a millennium. history class but make it math ⭐

Multiple RNDSPECs are evaluated left to right. order matters bestie, it always does.

Note that rounding isn't commutative, e.g. dateround 2012-03-01 Sat Sep -> 2012-09-03 vs. dateround 2012-03-01 Sep Sat -> 2012-09-01
Note that non-numeric strings prefixed with a - conflict with the command line options and a separating -- has to be used. put the -- in, she's begging you 😭

πŸ‘‘ OPTIONS πŸ‘‘

Recognized OPTIONs, let's go, one by one, no skips, no shortcuts:

  • -h, --help β€” Print help and exit. the classic.
  • -V, --version β€” Print version and exit. she'll tell you who she is πŸ’…
  • -q, --quiet β€” Suppress 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. so if you want silence, this is your girl 🀫
  • -f, --format=STRING β€” Output format. This can either be a specifier string (similar to strftime()'s FMT) or the name of a calendar. dress her up however you want ✨
  • -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. try on every outfit till one fits πŸŽ€
  • -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. the safety net fr fr
  • -e, --backslash-escapes β€” Enable interpretation of backslash escapes in the output and input format specifier strings.
  • -S, --sed-mode β€” Copy parts from the input before and after a matching date/time. Note that all occurrences of date/times within a line will be processed. she does the whole line, no crumbs.
  • -E, --empty-mode β€” Empty lines that cannot be parsed.
  • --locale=LOCALE β€” Format results according to LOCALE, this would only affect month and weekday names.
  • --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.
  • -z, --zone=ZONE β€” Convert dates printed on stdout to time zone ZONE, default: UTC. 🌍
  • -n, --next β€” Always round to a different date or time. no staying put, we're moving forward periodt πŸ”₯

🌈 FORMAT SPECS 🌈

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

However, due to a broader range of supported calendars dateutils must employ different rules.

πŸ“ 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)
  • %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
  • %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.
  • %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.
  • %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 (range 00 to 60, 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. she does not go back that far, do not ask πŸ’€

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, moreover, lilian/ldn and julian/jdn can also be used as input format string.


πŸŽ€ SPECIFYING DURATIONS πŸŽ€

Some tools (dateadd, dateseq) need durations as their input. Durations are generally incompatible with input formats as specified by -i|--input-format and (at the moment) the input syntax is fixed.

The general format is +-Nunit where + or - is the sign, N a number, and unit the unit as discussed below.

⭐ Units

  • s β€” seconds
  • m β€” minutes
  • h β€” hours
  • rs β€” real-life seconds, as in including leap transitions
  • d β€” days
  • b β€” business days
  • mo β€” months
  • y β€” years
For historical reasons, we used to accept m in the context of date-only input as a qualifier for months. As of 0.4.4, this is no longer the case. rip to a fallen icon 😭

πŸ”₯ EXAMPLES πŸ”₯

$ dateround 2012-03-01 2
2012-03-02
$
$ dateround -n 2012-03-01 1
2012-04-01
$
$ dateround 17:05:00 5m
17:05:00
$ dateround 17:04:00 /5m
17:05:00
$
$ dateround -n 17:04:00 4m
18:04:00
$ dateround -n 17:04:00 /1m
17:05:00
$

🫢 AUTHOR 🫢

Written by Sebastian Freundt <freundt@fresse.org> β€” thank you for your service king πŸ‘‘


πŸ™ˆ REPORTING BUGS πŸ™ˆ

Report bugs to: https://github.com/hroptatyr/dateutils/issues β€” she wants to hear about it, fr fr


🌸 SEE ALSO 🌸

The full documentation for dateround is maintained as a Texinfo manual. If the info and dateround programs are properly installed at your site, the command

info (dateutils)dateround

should give you access to the complete manual. go read the lore bestie πŸ“–βœ¨


and that's the whole vibe. this page is from dateutils 0.4.11, dated January 2024 β€” no cap, that's the version and that's the date, and dateround remains the main character she always was πŸ’…πŸŒˆπŸ¦‹