From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22652 invoked by alias); 14 Jul 2011 15:04:59 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 16133 Received: (qmail 16272 invoked from network); 14 Jul 2011 15:04:55 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) 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.1 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <110714080437.ZM14126@torch.brasslantern.com> Date: Thu, 14 Jul 2011 08:04:37 -0700 In-reply-to: <20110713195329.1fdc1b35@pws-pc.ntlworld.com> Comments: In reply to Peter Stephenson "Re: locking failed for /home/whoever/.zhistory: no such file or directory" (Jul 13, 7:53pm) References: <201107101653.p6AGrute004254@pws-pc.ntlworld.com> <20110713150103.2f5c6226@pwslap01u.europe.root.pri> <110713075444.ZM13017@torch.brasslantern.com> <20110713195329.1fdc1b35@pws-pc.ntlworld.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Subject: Re: locking failed for /home/whoever/.zhistory: no such file or directory MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Jul 13, 7:53pm, Peter Stephenson wrote: } Subject: Re: locking failed for /home/whoever/.zhistory: no such file or d } } On Wed, 13 Jul 2011 07:54:44 -0700 } Bart Schaefer wrote: } > } > I think he means zsh is never writing anything to the file, not that it } > is intentionally always empty. } } That's not related to the locking problem, though, is it? It might be -- that is, they might both stem from the same underlying cause, which is probably an issue with his system (perhaps his home directory permissions, for example, though I'm at a loss as to the exact reason). But the point is that his runtime history is non-empty and he's set SAVEHIST to a non-zero value, yet nothing is ever written to the file, so *something* is failing, and the only error he's seeing is the lock warning at startup. Maybe starting a login shell ("zsh -l" for those who don't know) from within another shell, and then exiting from that inner shell, would provide an opportunity to see error messages that are otherwise being hidden by the closing of a terminal emulator window or the like.