From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-5898-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 15079 invoked from network); 8 Feb 2003 19:05:02 -0000
Received: from sunsite.dk (130.225.247.90)
  by ns1.primenet.com.au with SMTP; 8 Feb 2003 19:05:02 -0000
Received: (qmail 27722 invoked by alias); 8 Feb 2003 19:04:34 -0000
Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 5898
Received: (qmail 27714 invoked from network); 8 Feb 2003 19:04:34 -0000
Received: from localhost (HELO sunsite.dk) (127.0.0.1)
  by localhost with SMTP; 8 Feb 2003 19:04:34 -0000
X-MessageWall-Score: 0 (sunsite.dk)
Received: from [4.46.181.248] by sunsite.dk (MessageWall 1.0.8) with SMTP; 8 Feb 2003 19:4:33 -0000
Received: (from schaefer@localhost)
	by candle.brasslantern.com (8.11.6/8.11.6) id h18J4ZI27967
	for zsh-users@sunsite.dk; Sat, 8 Feb 2003 11:04:35 -0800
From: "Bart Schaefer" <schaefer@brasslantern.com>
Message-Id: <1030208190435.ZM27966@candle.brasslantern.com>
Date: Sat, 8 Feb 2003 19:04:34 +0000
In-Reply-To: <20030207211639.GA10076@seas.upenn.edu>
Comments: In reply to Pavol Juhas <juhas@seas.upenn.edu>
        "[bug] 1000G in vi-mode" (Feb  7,  4:16pm)
References: <20030207211639.GA10076@seas.upenn.edu>
X-Mailer: Z-Mail (5.0.0 30July97)
To: zsh users <zsh-users@sunsite.dk>
Subject: Re: [bug] 1000G in vi-mode
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Feb 7,  4:16pm, Pavol Juhas wrote:
}
} I found the following bug in zsh 4.0.4:
} 
} If the current history number is less than 1000, zsh crashes after
} 1000G in vi command mode.

Hmm.  This appears to be a bug introduced in the 4.0 series.

In 3.0.7, `1000G' gives a feep.

In 4.0.6, it crashes here:

#0  0x806c307 in checkcurline ()
#1  0x806b1e3 in movehistent ()
#2  0x401a27aa in zle_goto_hist ()
#3  0x401a388e in vifetchhistory ()
#4  0x401a7697 in execzlefunc ()
#5  0x401a727d in zleread ()

In 4.1.0-dev-7, it neither feeps nor crashes.

} Also, I wonder if there is a way to completely reset history in the
} interactive session and start from event 1?

No, there isn't.