Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Add a note in the 'clock' man page about the interpretation of impossible values on [clock scan] |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | core-8-6-branch |
| Files: | files | file ages | folders |
| SHA3-256: |
8d69e2a5f20ec88a0c146aec2eac7542 |
| User & Date: | kbk 2018-07-21 18:45:09.956 |
Context
|
2018-07-26
| ||
| 15:51 | New test for [Bug ba921a8d98]. check-in: d498578df4 user: dgp tags: core-8-6-branch | |
|
2018-07-21
| ||
| 18:45 | Merge 8.6: Add a note in the 'clock' man page about the interpretation of impossible values on [cloc... check-in: 33d5f13bd6 user: kbk tags: core-8-branch | |
| 18:45 | Add a note in the 'clock' man page about the interpretation of impossible values on [clock scan] check-in: 8d69e2a5f2 user: kbk tags: core-8-6-branch | |
|
2018-07-20
| ||
| 15:58 | win: avoids warning by x64-build in function 'TclWinCPUID' - pointer targets in passing argument 1 o... check-in: edab70f507 user: sebres tags: core-8-6-branch | |
Changes
Changes to doc/clock.n.
| ︙ | ︙ | |||
449 450 451 452 453 454 455 456 457 458 459 460 461 462 | If a format string lacks a \fB%z\fR or \fB%Z\fR format group, it is possible for the time to be ambiguous because it appears twice in the same day, once without and once with Daylight Saving Time. If this situation occurs, the first occurrence of the time is chosen. (For this reason, it is wise to have the input string contain the time zone when converting local times. This caveat does not apply to UTC times.) .SH "FORMAT GROUPS" .PP The following format groups are recognized by the \fBclock scan\fR and \fBclock format\fR commands. .TP \fB%a\fR On output, receives an abbreviation (\fIe.g.,\fR \fBMon\fR) for the day | > > > > > > > > > > > > > | 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 | If a format string lacks a \fB%z\fR or \fB%Z\fR format group, it is possible for the time to be ambiguous because it appears twice in the same day, once without and once with Daylight Saving Time. If this situation occurs, the first occurrence of the time is chosen. (For this reason, it is wise to have the input string contain the time zone when converting local times. This caveat does not apply to UTC times.) .PP If the interpretation of the groups yields an impossible time because a field is out of range, enough of that field's unit will be added to or subtracted from the time to bring it in range. Thus, if attempting to scan or format day 0 of the month, one day will be subtracted from day 1 of the month, yielding the last day of the previous month. .PP If the interpretation of the groups yields an impossible time because a Daylight Saving Time change skips over that time, or an ambiguous time because a Daylight Saving Time change skips back so that the clock observes the given time twice, and no time zone specifier (\fB%z\fR or \fB%Z\fR) is present in the format, the time is interpreted as if the clock had not changed. .SH "FORMAT GROUPS" .PP The following format groups are recognized by the \fBclock scan\fR and \fBclock format\fR commands. .TP \fB%a\fR On output, receives an abbreviation (\fIe.g.,\fR \fBMon\fR) for the day |
| ︙ | ︙ |