From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-43801-ml=inbox.vuxu.org@zsh.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED,
	DKIM_VALID,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham
	autolearn_force=no version=3.4.2
Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2])
	by inbox.vuxu.org (OpenSMTPD) with ESMTP id e5d5eaaf
	for <ml@inbox.vuxu.org>;
	Wed, 7 Nov 2018 22:27:12 +0000 (UTC)
Received: (qmail 20657 invoked by alias); 7 Nov 2018 22:27:01 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
List-Unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
X-Seq: 43801
Received: (qmail 19308 invoked by uid 1010); 7 Nov 2018 22:27:01 -0000
X-Qmail-Scanner-Diagnostics: from mail-lj1-f177.google.com by f.primenet.com.au (envelope-from <schaefer@brasslantern.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(209.85.208.177):SA:0(-2.0/5.0):. 
 Processed in 4.638107 secs); 07 Nov 2018 22:27:01 -0000
X-Envelope-From: schaefer@brasslantern.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=brasslantern-com.20150623.gappssmtp.com; s=20150623;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=zSNSFdXKfSLOgwazdxkVU95ohpeYUMAd00cZ/D5irS4=;
        b=iIxAkno1HI2v+gu18tENsM6Lf/MhzvlNKaIxftCeV9JbtQ/HXNIeGg0lVA7WoVA72L
         jTV3YQy757NXZqfE6R7TImKA8yE6JLtwBdZ5CyRiKPswTONiNkSfDCX2RtOn6e/iDZ9P
         EOVE9v6JM1ug5VQdLLlt1K7VkSWxkMG+zg+Ykc8HcbMcEqoZdD0GFkxkaH/ZJimFRLpD
         US0V6c5Nl1YFUaAazhQk6ws08wRsRG3kK1P8EM+qZxNWj/4l+wJjMNRFX7zT3ynW+Yt/
         K53vxTl0jv/D5b9b6+uXUrD7T0P8es792grkYEEPi72E5bLJdZd7r95OOCl1msv7kBRX
         /ROg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=zSNSFdXKfSLOgwazdxkVU95ohpeYUMAd00cZ/D5irS4=;
        b=m+DfMecvHSQXm2bTIx0L7uhcGqN7lrCPk5H2SD5gn43y6saBeigM8V7yGOEF1fGksq
         saLz3Rnjv5zCxqmAA6AzWC1+FTN6sm4U5QKcYuSYBeQ0OXaiI2hq3MZfW/T9ai9o/q7z
         0NQaCrkPa2G8nsBrYYW9ob09jgJgSNuD16Olftw6XTLm8UIbc8oTaHj/UQfWUg7tKSS6
         vYgCBh8MPY2hUp3ESPt8R04RJ/7XBy4kbRlqHmm5r1wAHZEuv5H9c+P4aoOl2+4bGZQg
         /Joq8pb/bGPitLNRqmyusOMySOI9kM3mokwRWz9dIrtZrto6dmL02POpoc9zHvuCj7e0
         V/2Q==
X-Gm-Message-State: AGRZ1gJtbA7EkYUgr9PThmXf+yp5hiDWdPWRKL/RgZt8aRIUBhqUCuq2
	Z9gYj2+jSItwa51SWlji8Ab4bA/mjRLn8tGf9oJegQ==
X-Google-Smtp-Source: AJdET5funq7Dsb7XvSl2k9tq04BBTgxDlPF1ZPXhbaDIaBzO08QB47p0rlQsLAqmtOVrRyiTWRzUDp/sdo3ZOiMyveI=
X-Received: by 2002:a2e:630a:: with SMTP id x10-v6mr1180919ljb.11.1541629611783;
 Wed, 07 Nov 2018 14:26:51 -0800 (PST)
MIME-Version: 1.0
References: <A2485F5D-2B26-48BE-B695-2328DF86179D@dana.is>
In-Reply-To: <A2485F5D-2B26-48BE-B695-2328DF86179D@dana.is>
From: Bart Schaefer <schaefer@brasslantern.com>
Date: Wed, 7 Nov 2018 14:26:39 -0800
Message-ID: <CAH+w=7ZLNRfC11UVPxLSYwQu9EeQ3vVtE8DC3FruknSkSW1c9Q@mail.gmail.com>
Subject: Re: [PATCH] Add nanosecond support to strftime (zsh/datetime)
To: dana <dana@dana.is>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Content-Type: text/plain; charset="UTF-8"

On Wed, Nov 7, 2018 at 2:19 PM dana <dana@dana.is> wrote:
>
> This is a follow-up to workers/43075, which added nanosecond support to (AFAIK)
> the rest of the shell.

I'm having flashbacks that a new format specifier for this may have
been discussed on the austin-group (POSIX standards) mailing list.  If
so, it would be preferable to match here whatever the (still
forthcoming?  I've lost track of austin-group recently) standard is
going to be, rather than invent something of our own.