From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7387 invoked by alias); 25 Apr 2014 15:26:43 -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: X-Seq: 32582 Received: (qmail 14523 invoked from network); 25 Apr 2014 15:26:36 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <140425082635.ZM12243@torch.brasslantern.com> Date: Fri, 25 Apr 2014 08:26:35 -0700 In-reply-to: <20140425093525.3754a495@pwslap01u.europe.root.pri> Comments: In reply to Peter Stephenson "Re: zsh got stuck without any message because of history lock file" (Apr 25, 9:35am) References: <53594068.4040503@googlemail.com> <140424100228.ZM10689@torch.brasslantern.com> <140424220232.ZM11424@torch.brasslantern.com> <20140425093525.3754a495@pwslap01u.europe.root.pri> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: zsh got stuck without any message because of history lock file MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Apr 25, 9:35am, Peter Stephenson wrote: } } On Thu, 24 Apr 2014 22:02:32 -0700 } Bart Schaefer wrote: } > However, this would mean that every zsh that is accessing the same } > HISTFILE has to be using the same locking options. Is that OK? } } It's fairly easy to get inconsistent shell options, however. I suppose } we could think about simple tests to see if it looks like it's been } locked a different way and print a warning. That shouldn't be too difficult code-wise, but will require calling lstat() on the .LOCK file name (ignoring failure thereof). I'm going to go ahead and commit 32580 while we think about it.