From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20358 invoked by alias); 10 Jul 2011 17:13:51 -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: 16125 Received: (qmail 13116 invoked from network); 10 Jul 2011 17:13:49 -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: <110710101331.ZM8581@torch.brasslantern.com> Date: Sun, 10 Jul 2011 10:13:31 -0700 In-reply-to: Comments: In reply to Cesar Romani "locking failed for /home/whoever/.zhistory: no such file or directory" (Jul 10, 9:22am) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Cesar Romani , zsh-users@zsh.org 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 10, 9:22am, Cesar Romani wrote: } Subject: locking failed for /home/whoever/.zhistory: no such file or direc } } I'm using zsh 4.3.12-dev-1 } Whenever I start zsh I always get the following message: } zsh: locking failed for /home/whoever/.zhistory: no such file or } directory: reading anyway This probably means that your system doesn't support zsh's preferred form of locking, so zsh is trying to create a file in the directory named by your $TMPPREFIX. Does *that* directory exist? What do you see if you run print =(:) ? Do you change TMPPREFIX at any time in your startup files?