From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by melb.werple.net.au (8.7.5/8.7.3) with ESMTP id DAA22326 for ; Thu, 11 Apr 1996 03:22:32 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id NAA13498; Wed, 10 Apr 1996 13:09:00 -0400 (EDT) Resent-Date: Wed, 10 Apr 1996 13:09:00 -0400 (EDT) From: Anthony Heading Message-Id: <199604101708.SAA00191@gmp-etpres1.uk.jpmorgan.com> Subject: Re: History file locking? To: schaefer@z-code.ncd.com Date: Wed, 10 Apr 1996 18:08:21 +0100 (BST) Cc: zsh-workers@math.gatech.edu In-Reply-To: <960410092605.ZM16040@zyrcon.z-code.com> from "Barton E. Schaefer" at Apr 10, 96 09:26:05 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"Kf6_F2.0.qI3.ii-Qn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/910 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu > It's actually possible to do .lock locking *more* reliably than lockf > if you follow some special rules. [...] > > However, Zefram is right that it's probably more effort than it's worth. More than it's worth for the history. But wouldn't it make a rather nice general-purpose builtin? `lockfile' from procmail is a pretty useful utility - to have equivalent functionality in zsh would be great. Anthony