From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-35240-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 21809 invoked by alias); 20 May 2015 17:31:45 -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: 35240
Received: (qmail 6286 invoked from network); 20 May 2015 17:31:43 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,
	RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.0
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:from:message-id:date:in-reply-to:comments
         :references:to:subject:cc:mime-version:content-type;
        bh=WJaVGa8iu0Ih9L75sj8uaZpVtrY8zk1mUc2CdpXUQmI=;
        b=LcjQnNOVdyOtxCDI+uFJ98hiE2vJlsCcy3DwO13/NZp8P7XOEuMYOv0EitmCVZTeDZ
         CwM6NL5jxECy5ruYmjqSg3bFl5Tjqgpx2OREDRZ0N1c0GnuIKI5lzttUe2itWPDE+o/b
         6uqpMkx/MvvqN41c3o1vjhHpCXi2tQLdydpnbKwJeNV9es1xxGlNPiKEmSBO+Q+QkzO5
         nFb3ajLYXkmiHvt4JciwfD1iYjuXrwu3sEy0TuLjy1hWlq2sHB0D0Lg5b/n4rUJSslrG
         UI69FQYbg2ePiDMUi981wNEKMhZEE+4Nqkkxd32l/dOYb3aNO3zjBEybdlXnMAUKuEcz
         Rtmg==
X-Gm-Message-State: ALoCoQmvGtG3aXbv+IGHKzxym8a3ujQ6qoMiQiHq4kMK9TWPD3DestaBpkiavVwvbFlpMPqXy5KX
X-Received: by 10.182.91.35 with SMTP id cb3mr29882913obb.87.1432143099629;
        Wed, 20 May 2015 10:31:39 -0700 (PDT)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <150520103136.ZM26727@torch.brasslantern.com>
Date: Wed, 20 May 2015 10:31:36 -0700
In-Reply-To: <CAHYJk3Qgm=Mc3_d+kC-1hB7ybxcqU43nnr7Hw=N-opXj7nDa8A@mail.gmail.com>
Comments: In reply to Mikael Magnusson <mikachu@gmail.com>
        "Re: "{ } always { }" construct and return in called functions" (May 19,  8:22am)
References: <CAHfspHmUOgLjnEMtLBBoeU31Z2GKu8uD5MYE4jsogMKbf+ag9g@mail.gmail.com> 
	<20150513155915.71f3daaa@pwslap01u.europe.root.pri> 
	<CAHYJk3RBn_U_ZTNXWHeBfAJyibspcx1=gMM2OTmXz2cpsrrY2Q@mail.gmail.com> 
	<20150518131401.2db3aefa@pwslap01u.europe.root.pri> 
	<CAHYJk3QCxkpN_G2yAXW0S+J8BnV4O3OFTpPHAg9+ajuJ3RXb1A@mail.gmail.com> 
	<20150518134704.0a7f4293@pwslap01u.europe.root.pri> 
	<150518220408.ZM7475@torch.brasslantern.com> 
	<CAHYJk3Qgm=Mc3_d+kC-1hB7ybxcqU43nnr7Hw=N-opXj7nDa8A@mail.gmail.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: "{ } always { }" construct and return in called functions
Cc: Mikael Magnusson <mikachu@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On May 19,  8:22am, Mikael Magnusson wrote:
} Subject: Re: "{ } always { }" construct and return in called functions
}
} On Tue, May 19, 2015 at 7:04 AM, Bart Schaefer
} > If you have some other job running in the background, the shell does
} > not exit when 'exit' is called from a zle widget:
} 
} A good theory, but
} zshrun ~> echo $options[checkjobs]
} off
} I've always had that option turned off.
} 
} Also, since the command is run with &| then surely there are no jobs
} either way?

I was presuming that whatever other job was preventing the exit had been
started somewhere earlier in the startup sequence, and was not the same
job started by _accept_and_quit.

} It seems to be run once in the background by the widget, and then
} another one in the foreground that I can ctrl-c out of. I only press
} enter the one time.

This makes me suspect that both _accept_and_quit and also accept-line
are being executed.

Perhaps the shell is receiving "\r\n" and executing _accept_and_quit on
the \r followed by accept-line on the \n ?

Try

    zsh -c "${BUFFER}" &|
    BUFFER=""
    exit

??