From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 21374 invoked from network); 4 Jun 2020 02:36:21 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 4 Jun 2020 02:36:21 -0000 Received: (qmail 16304 invoked by alias); 4 Jun 2020 02:36:11 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 45957 Received: (qmail 15715 invoked by uid 1010); 4 Jun 2020 02:36:11 -0000 X-Qmail-Scanner-Diagnostics: from mail-oi1-f182.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25828. spamassassin: 3.4.4. Clear:RC:0(209.85.167.182):SA:0(-1.9/5.0):. Processed in 3.171955 secs); 04 Jun 2020 02:36:11 -0000 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.167.182 as permitted sender) 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=xsswuXCPjHZQzVM+wJmrhFHiGFVGjcjV5ZCfOxQYEWw=; b=fTRwPAZIa+MC4oDHPkgfIPkuoy5NZvRh7so0BcDPVEXHbL7xPb8Xb3zDJpgJQfL+r+ S4f7ivFa4v03irdQpkusL66WS5BvG21YSUQ/iUlNyV9ufXs/y7FF1zxKIon7rWtfQh+M nHaAKlbQ5DQ+vb/j2qjC1vWQuhkv15q9RCR4KuVWY1ELm05UEoaRApJ98AaYrt41X6zM ctcUVY9fPM6RpssDebKs3irpb3f4YhmJSbK6BmOm4qhF/TaFCwJgrlTxT5HoovBnXlaD /FQHgOY4MVmB3+pUhLRzD3NjmSZRw9hxu9nszrfYY4vTtpaIY8VOuVqiZEPaoFLnbEYz zTtQ== X-Gm-Message-State: AOAM532Z85v0PeA5TpAqsAFMvjhCmYllxcEbm0W/jUO1M1byI7fxsBDn xl8+xrHD3oHIiQM3SsIMlNNLBpwN9hQigkrWDJUbXA== X-Google-Smtp-Source: ABdhPJx1LpbSXz97Itv/SEzgCjPsioqb3Dp3zj7qGNUUwv6LLbNFnxkZ5OMzvbeJL7RbsOGlan7TllHci1Y5ZGppndM= X-Received: by 2002:a05:6808:6d1:: with SMTP id m17mr1842949oih.132.1591238135095; Wed, 03 Jun 2020 19:35:35 -0700 (PDT) MIME-Version: 1.0 References: <89aed74d-db7b-47ad-b218-8158838049e9@www.fastmail.com> <94e73ebcf39d4d3f9c7ae257b1d75d16@CAMSVWEXC01.scsc.local> In-Reply-To: From: Bart Schaefer Date: Wed, 3 Jun 2020 19:35:23 -0700 Message-ID: Subject: Re: Any way to allow clobbering empty files when noclobber is set? To: Vin Shelton Cc: Peter Stephenson , Martin Tournoij , "zsh-workers@zsh.org" Content-Type: text/plain; charset="UTF-8" On Wed, Jun 3, 2020 at 7:14 PM Vin Shelton wrote: > > If we want to support this feature, why don't we change the meaning of > NO_CLOBBER to mean only non-empty files? What is the significance of a > 0-length file as opposed to a file with contents? Timestamps.