Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh crashes with floating point exception
- X-seq: zsh-users 12232
- From: Peter Stephenson <pws@xxxxxxx>
- To: Zsh users list <zsh-users@xxxxxxxxxx>
- Subject: Re: zsh crashes with floating point exception
- Date: Mon, 19 Nov 2007 17:06:57 +0000
- In-reply-to: <20071119165855.GD29766@xxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20071119142811.GF12829@xxxxxxxxx> <200711191514.lAJFEb7E003678@xxxxxxxxxxxxxx> <20071119155749.GA29766@xxxxxxxxx> <200711191624.lAJGOcA1018650@xxxxxxxxxxxxxx> <20071119163151.GC29766@xxxxxxxxx> <200711191645.lAJGjCeF018958@xxxxxxxxxxxxxx> <20071119165855.GD29766@xxxxxxxxx>
Andy Spiegl wrote:
> lama:~>which backward-kill-line
> backward-kill-line () {
> local scb=$CUTBUFFER
> local slw=$LASTWIDGET
> local sbl=${#BUFFER}
> zle .backward-kill-line
> (( $sbl == $#BUFFER )) && return
> if [[ $slw = (.|)(backward-|)kill-* ]]
> then
> killring=("${(@)killring[2,-1]}")
> CUTBUFFER=$CUTBUFFER$scb
> fi
> set-x-clipboard $CUTBUFFER
> }
Aha. If, for whatever reason, that ends up setting "killring=()", then
the bug I spotted will trigger, with possible symptoms like the ones you
saw (it's system-dependent---some OSes won't care). So there's a good
chance that was the correct fix.
--
Peter Stephenson <pws@xxxxxxx> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
Messages sorted by:
Reverse Date,
Date,
Thread,
Author