From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18374 invoked from network); 2 Oct 1999 17:45:45 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 Oct 1999 17:45:45 -0000 Received: (qmail 8779 invoked by alias); 2 Oct 1999 17:45:34 -0000 Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 2647 Received: (qmail 8771 invoked from network); 2 Oct 1999 17:45:33 -0000 From: "Bart Schaefer" Message-Id: <991002174520.ZM29846@candle.brasslantern.com> Date: Sat, 2 Oct 1999 17:45:20 +0000 In-Reply-To: <991002173314.ZM29781@candle.brasslantern.com> Comments: In reply to "Bart Schaefer" "Re: monitoring the shell prompt" (Oct 2, 5:33pm) References: <19991002150327.A11347@wigner.cstc.org> <991002173314.ZM29781@candle.brasslantern.com> X-Mailer: Z-Mail (5.0.0 30July97) To: pumilia@est.it, zsh-users@sunsite.auc.dk Subject: Re: monitoring the shell prompt MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Oct 2, 5:33pm, Bart Schaefer wrote: } Subject: Re: monitoring the shell prompt } } is a nasty hack to force the editor to restart in command mode after the } send-break; send-break stops all zle processing Ahem. To explain about that: I was at first using send-break instead of accept-line, which beeped horribly, and forgot to edit the description after I realized that accept-line would also work and work silently. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com