From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-32786-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 1944 invoked by alias); 23 Jun 2014 10:04:38 -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: 32786
Received: (qmail 5643 invoked from network); 23 Jun 2014 10:04:27 -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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,FREEMAIL_REPLY,HTML_MESSAGE,
	RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=QUp1IZ9pyKLBD+3IZZRRxP/BebfxRTNz2cCXrJ+5eHo=;
        b=daCZJtCV4XuqMbEdu3/9szkvO4kW2R/mmNI/VKp28KRX8UmyILi0thKG+Arge/qjAB
         wqAbWfz1pSkq5q2LJi8Vbn02ntsOcBZXV9ZAq4ydk1mMZklVbIkcZkTKjBboeyhOilly
         ILC128DTfJGBcmelBfvojn1G9FCQB/klcfzH2QaY1A7Nqx9CYEd1fr5KCEKmEcAWsj7B
         ugTCrOznUyWACf8b8Uw58/MpNoXbcVuynF4ao4LEXJGP3e5fHIP513pd3kRMcC2VN8DD
         KggjyRdArBkb8zyT13NwUld0uu2WH2Jg+sn3/7HrLBoPb67lDi5fwXqdTt/0G0oaTBgR
         a0NA==
X-Received: by 10.194.222.230 with SMTP id qp6mr26008512wjc.23.1403515987854;
 Mon, 23 Jun 2014 02:33:07 -0700 (PDT)
MIME-Version: 1.0
From: Arjen Rouvoet <a.j.rouvoet@gmail.com>
Date: Mon, 23 Jun 2014 11:32:47 +0200
Message-ID: <CAOs3h-0LBBOCLzG+vh1AYmLtKmr1VEYXquDSVjrx4JjsQCBWFw@mail.gmail.com>
Subject: BUG: ZSH freezes (on history) when systime is wrong
To: zsh-workers@zsh.org
Content-Type: multipart/alternative; boundary=001a11c3bad8e48d9804fc7d8781

--001a11c3bad8e48d9804fc7d8781
Content-Type: text/plain; charset=ISO-8859-1

Last weekend I had the problem that I could no longer start a terminal/load
a tty, because
zsh was freezing on it's init.

After booting into emergency mode, and setting my shell to bash, I got
control back, and tried to narrow down the issue.
Zero'ing out parts of my config, I narrowed it down to the history
sesttings, in particular: when I changed the path to the hist file, it
loaded (and exited; because after backing up and creating a new histfile,
zsh loaded but froze on exit).

At that point I noticed the system time was messed up (propably by windows
usage).
After syncing, zsh worked fine again with the original history file.

I wonder if the history contained some timestamp in the future, which got
zsh confused.
But in any case, I thought it was a bug worth mentioning.

With regards,



Arjen Rouvoet
*a.j.rouvoet@gmail.com <a.j.rouvoet@gmail.com>*

--001a11c3bad8e48d9804fc7d8781--