From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-32574-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 8823 invoked by alias); 24 Apr 2014 16:49:21 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 32574
Received: (qmail 11288 invoked from network); 24 Apr 2014 16:48:47 -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=-0.9 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,T_DKIM_INVALID,
	T_TO_NO_BRKTS_FREEMAIL autolearn=no version=3.3.2
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        bh=254tdYLGnt0XAURxClOVqnb11iT/6LLp92q5SQux6qg=;
        b=NuhdWrS08y1Q9ox2S+BDo/X/dzjpErz9isfx0UEn5Cls7lEJmF2WnQPs0PCcKAk65R
         Thq1dlUcePejYglxM/Iz0Q6rg6mdi5EpG1oVQimIKwhVq0jz50NDe4FYZ88Bm8zX6A9c
         PU1J7FpSZ3R2wSde2stC5hzct/TTBTRsmCWipMSY/iD3Ko2Y0Vs6cBlYbRleFNre9hoq
         IOhdeZRyqKYSxM9hf+Wh7iDsDR/ZBdZiAsQKrt6H7UsOIzNWiNjy9uJFnVorp6EIHs7u
         7V2kSAqXaYjv93bADTWUIAP8rUFTNuLbC61He629Vs5iCyfZsnN0HZJ2zjqxuYkoixHp
         GbLQ==
X-Received: by 10.112.157.67 with SMTP id wk3mr1130417lbb.63.1398358123145;
        Thu, 24 Apr 2014 09:48:43 -0700 (PDT)
X-Google-Original-From: Andreas <klingt.net@googlemail.com>
Message-ID: <53594068.4040503@googlemail.com>
Date: Thu, 24 Apr 2014 18:48:40 +0200
From: Andreas <klingt.net@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: zsh-workers@zsh.org
Subject: zsh got stuck without any message because of history lock file
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

My zsh got stuck without any error message, because the 
~/.zsh-history.LOCK file wasn't deleted after a system crash. This is a 
real problem if one uses zsh as default shell and therefore can't 
execute any command. Luckily i was able to open a bash terminal and used 
strace to determine why zsh doesn't respond.
Please add an error message or prompt the user, if the lock should be 
deleted.

I'm using zsh "5.0.5 (x86_64-unknown-linux-gnu)" on Arch Linux with 
Kernel 3.14.1-1-ARCH x86_64.

Andreas Linz