In doc, discourage alphabetic tz abbrs in Gnus

This commit is contained in:
Paul Eggert 2026-08-31 10:10:02 -07:00
parent 6dfaa91c28
commit 2f7c5e4de0
2 changed files with 4 additions and 4 deletions

View file

@ -18335,12 +18335,12 @@ As a special case, a star in either @code{Dom} or @code{Dow} doesn't
mean ``all possible values'', but ``use only the other field''. Note
that if both are star'ed, the use of either one gives the same result.
@item
The @code{Time-Zone} header is special in that it can only have one
The @code{Time-Zone} header is special in that it can have only one
value (@code{GMT}, for instance). A star doesn't mean ``all possible
values'' (because it makes no sense), but ``the current local time
zone''. Most of the time, you'll be using a star here. However, for a
list of available time zone values, see the variable
@code{nndiary-headers}.
Universal Time entry, you can use @code{GMT}, @code{UT}, @code{UTC} or
@code{Z}.
@end itemize
As a concrete example, here are the diary headers to add to your message

View file

@ -1201,7 +1201,7 @@ all. This may very well take some time.")
;; Parse the cron-like value of header X-Diary-HEAD in current buffer.
;; - Returns nil if `*'
;; - Otherwise returns a list of integers and/or ranges (BEG . END)
;; The exception is the Timze-Zone value which is always of the form (STR).
;; The exception is the Time-Zone value which is always of the form (STR).
;; Signals are caught by `nndiary-schedule'.
(let ((header (format "^X-Diary-%s: \\(.*\\)$" head)))
(goto-char (point-min))