From: Eli Zaretskii <eliz@gnu.org>
To: "Rüdiger Sonderfeld" <ruediger@c-plusplus.de>
Cc: andrea.rossetti@gmail.com, 15816@debbugs.gnu.org
Subject: bug#15816: 24.3; (format-time-string "%h") returns "" instead of month
Date: Wed, 06 Nov 2013 19:26:56 +0200 [thread overview]
Message-ID: <8361s57867.fsf@gnu.org> (raw)
In-Reply-To: <3369232.afZtqa4znz@descartes>
> From: Rüdiger Sonderfeld <ruediger@c-plusplus.de>
> Cc: andrea.rossetti@gmail.com, 15816-done@debbugs.gnu.org
> Date: Wed, 06 Nov 2013 14:31:04 +0100
>
> I just compared the docstring to the manpage of strftime on GNU/Linux and the
> following symbols are not ANSI C
>
> - %C is SU
> - %G,%g are TZ
> - %h is SU (%b)
> - %e is SU (%d with blanks)
> - %u is SU
> - %V is SU
> - %k is TZ (%H with blanks)
> - %l is TZ (%I with blanks)
> - %N not in manpage or glibc manual
> - %z is SU
> - %s is TZ
> - %D is SU ("%m/%d/%y", should not be used)
> - %T is SU ("%H:%M:%S")
> - %R is SU ("%H:%M")
> - %r is SU ("%I:%M:%S %p")
> - %t is SU (\t)
> - %n is SU (\n)
>
> (SU :: Single UNIX Specification and TZ :: Olson's timezone package)
>
> Maybe we should not mention %h, %D, %T, %R, %r, %t, %n at all because these
> can be replaced by the portable alternatives mentioned. The rest might be a
> bit tricky to replace. Could you try which of them work on Windows at all?
> (Sorry I don't have a current Windows Emacs available.)
All of them are supported, with the single exception of %r.
next prev parent reply other threads:[~2013-11-06 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 0:05 bug#15816: 24.3; (format-time-string "%h") returns "" instead of month andrea.rossetti
2013-11-06 0:48 ` Stefan Monnier
2013-11-06 6:46 ` Bastien
2013-11-06 10:16 ` Eli Zaretskii
2013-11-06 10:16 ` Eli Zaretskii
2013-11-06 13:31 ` Rüdiger Sonderfeld
2013-11-06 14:16 ` Andreas Schwab
2013-11-06 17:12 ` Stefan Monnier
2013-11-06 17:26 ` Eli Zaretskii [this message]
2013-11-16 0:01 ` Rüdiger Sonderfeld
2013-12-11 14:42 ` Rüdiger Sonderfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8361s57867.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15816@debbugs.gnu.org \
--cc=andrea.rossetti@gmail.com \
--cc=ruediger@c-plusplus.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).