From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: ISO date in attribution line
Date: Tue, 11 Jun 2002 12:51:13 +0200 [thread overview]
Message-ID: <vafadq2ulzy.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <E17HSlz-00081w-00@eris.void.at> (Andreas Fuchs's message of "Mon, 10 Jun 2002 19:16:07 +0200")
Andreas Fuchs <asf@void.at> writes:
> Today, Kai Großjohann <Kai.Grossjohann@cs.uni-dortmund.de> wrote:
>> lawrence mitchell <0198183+ding@sms.ed.ac.uk> writes:
>>> Elegant though it is, not quite, since encode-time doesn't like a
>>> list, it wants each argument separetely, at least it does in 21.2
>>> and 20.4, which is odd, since the doc-string claims that it's the
>>> reverse of decode-time, which returns a list.
>>
>> Ah, I missed that.
>>
>> (apply 'encode-time (parse-time-string date)) should fix it.
>
> Doesn't, sorry. encode-time complains because of non-integer values
> (and inded, parse-time-string of the string passed from the TC function
> yields nil values in its result list. that is because only the day,
> month and year are contained in the string.
Ah, hm. parse-time-string leaves nil values, right? Hm.
I guess that one needs to call parse-time-string, extract the ymd
values from it, anyway. Then it doesn't matter if one uses format on
those values directly, rather than calling encode-time with the three
values and a lot of zeros and then calling format-time-string on that.
Whee. I wish it was easier to use format-time-string here.
kai
--
~/.signature is: umop 3p!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-06-11 10:51 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 15:59 The followup will show the bug Kai Großjohann
2002-05-24 21:45 ` Reiner Steib
2002-05-25 17:22 ` Kai Großjohann
2002-05-25 17:49 ` Oystein Viggen
2002-05-27 13:47 ` Christopher Splinter
2002-05-27 14:40 ` Kai Großjohann
2002-05-27 15:32 ` Oystein Viggen
2002-05-27 19:07 ` Paul Jarc
2002-05-28 11:06 ` Christopher Splinter
2002-05-28 6:30 ` Niklas Morberg
2002-05-28 7:30 ` he " Marco Lonsing
2002-05-28 7:38 ` The " David Kågedal
2002-05-28 7:38 ` David Kågedal
[not found] ` <u5tptzg90xj.fsf@leeloo.hq.vtech>
2002-05-28 8:12 ` Ronan Waide
2002-05-28 22:24 ` Alex Schroeder
2002-05-28 9:21 ` Kai Großjohann
2002-05-29 9:33 ` Niklas Morberg
2002-05-28 11:03 ` Christopher Splinter
2002-05-27 17:59 ` Jesper Harder
2002-05-28 13:01 ` Kai Großjohann
2002-05-28 13:31 ` Kai Großjohann
2002-05-28 13:31 ` Kai Großjohann
2002-05-28 16:36 ` Jesper Harder
2002-05-29 7:38 ` Kai Großjohann
2002-05-29 18:26 ` Johann Gambolputty de von ausfern schplenden schlitter...von Hautkopft of Ulm
2002-05-29 20:11 ` Jesper Harder
2002-05-30 9:57 ` Kai Großjohann
2002-05-30 10:01 ` Kai Großjohann
2002-05-30 9:56 ` Kai Großjohann
2002-05-28 17:36 ` Christopher Splinter
2002-05-25 20:28 ` Andreas Fuchs
2002-06-09 18:04 ` ISO date in attribution line (Was: Re: The followup will show the bug.) Svend Tollak Munkejord
2002-06-09 18:35 ` ISO date in attribution line Andreas Fuchs
2002-06-09 19:40 ` Kai Großjohann
2002-06-09 20:22 ` lawrence mitchell
2002-06-10 9:36 ` Kai Großjohann
2002-06-10 17:16 ` Andreas Fuchs
2002-06-11 10:51 ` Kai Großjohann [this message]
2002-06-09 20:40 ` Andreas Fuchs
2002-06-09 20:59 ` Svend Tollak Munkejord
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vafadq2ulzy.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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.
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 NNTP newsgroup(s).