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=FREEMAIL_FROM, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 19183 invoked from network); 4 Jun 2020 02:14:48 -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:14:48 -0000 Received: (qmail 14679 invoked by alias); 4 Jun 2020 02:14:42 -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: 45956 Received: (qmail 8985 invoked by uid 1010); 4 Jun 2020 02:14:42 -0000 X-Qmail-Scanner-Diagnostics: from mail-ot1-f52.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.210.52):SA:0(-1.4/5.0):. Processed in 1.769223 secs); 04 Jun 2020 02:14:42 -0000 X-Envelope-From: ethersoft@gmail.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.210.52 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=oXbrxkUvaiG4ElDDgJcwt37OCWm1jnyfi5pqJETTwlQ=; b=QbXm4N/NvCuEAHGtpSXbSjhIaMGvPqIcwAn+3pZe0mzUhiCmEcTS1A3FmrvTQ0uSC+ BKy2WOW32g2gFdPBoWIKjPn4VzWNbd5bMUziDKqK3MML3PpnHLzCJT893Mor0L9+VpIu g22O0Ve5ZhqAJgs8ZeFqT6mmKzJvR9HQTNishu5bwjDDb2KEyy+9HKz0wtfBE3yD5Pp8 D+zhO8Tp+11AddanlgnkKqV+2KujMMM5lJrg/Qp3Y4150x+ZrxK628BNPh82kZjohDhV FOzlWzch5PCXi1s3WY2m5TCMjoBNk8XXz1h+6gOR4P9zwcOmaXhCmwSnY02B8AurCCvl BFIA== X-Gm-Message-State: AOAM532b3znHQfkwyrntcKXunCUlVabvFnsl+vILs2DJgn65+FerV2f3 gIVWIVWrTKiZTzDsZrbOgRg29PDDBZWxmoy6SaA= X-Google-Smtp-Source: ABdhPJxkZrI6OMqPSvN/9agNzn0MBcw6ywEx8pBbdkxdQ2DOjZ4gbQESzrlTyaWsZ8VMODVTfKEXx5x3t6fwWblwdV8= X-Received: by 2002:a9d:37a2:: with SMTP id x31mr2261784otb.255.1591236847496; Wed, 03 Jun 2020 19:14:07 -0700 (PDT) MIME-Version: 1.0 References: <89aed74d-db7b-47ad-b218-8158838049e9@www.fastmail.com> <94e73ebcf39d4d3f9c7ae257b1d75d16@CAMSVWEXC01.scsc.local> In-Reply-To: <94e73ebcf39d4d3f9c7ae257b1d75d16@CAMSVWEXC01.scsc.local> From: Vin Shelton Date: Wed, 3 Jun 2020 22:13:31 -0400 Message-ID: Subject: Re: Any way to allow clobbering empty files when noclobber is set? To: Peter Stephenson Cc: Martin Tournoij , "zsh-workers@zsh.org" Content-Type: multipart/alternative; boundary="0000000000000c702705a738b341" --0000000000000c702705a738b341 Content-Type: text/plain; charset="UTF-8" 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? - Vin On Wed, Jun 3, 2020 at 8:05 AM Peter Stephenson wrote: > Martin Tournoij wrote: > > I switched from tcsh to zsh a while ago (many years too late, I know), > > and found zsh can do pretty much everything better. There's one thing > > I rather miss though: the 'notempty' option in 'noclobber'. > > This isn't actually hard to implement. What does everyone else think? > > pws > --0000000000000c702705a738b341--