From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27443 invoked from network); 2 Jan 2000 00:55:24 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 Jan 2000 00:55:24 -0000 Received: (qmail 7484 invoked by alias); 2 Jan 2000 00:55:14 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9178 Received: (qmail 7477 invoked from network); 2 Jan 2000 00:55:13 -0000 Subject: Re: Possible bug? In-Reply-To: <20000101030505.A1857@mindcrime.corp.ef.net> from Mike Perez at "Jan 1, 2000 03:05:05 am" To: Mike Perez Date: Sun, 2 Jan 2000 00:55:09 +0000 (GMT) CC: zsh-workers@math.gatech.edu X-Mailer: ELM [version 2.4ME+ PL65 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: From: Zefram Mike Perez wrote: >Well I am not sure if this is a bug or not, but I was able to reproduce >it on a few machines that all were in Y2K. I can reproduce it too: % date Sun Jan 2 00:48:08 GMT 2000 % print -P '%D{%G}' 1999 % date +%G 1999 % date +%Y 2000 % print -P '%D{%Y}' 2000 What is %G, anyway? It's not one of the zsh extensions; it's just being handled by the native strftime(3). My strftime(3) doesn't document %G, and I don't have its source handy. I expect that %G is the year part of the week specification for the current week; today is 1999-W52-7, and 2000-W01 starts tomorrow (2000-01-03 == 2000-W01-1). Ah, look: % date -d tomorrow Mon Jan 3 00:52:44 GMT 2000 % date -d tomorrow +%G 2000 -zefram