From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8273 invoked from network); 16 May 2000 06:28:35 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 16 May 2000 06:28:35 -0000 Received: (qmail 13367 invoked by alias); 16 May 2000 06:28:26 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11399 Received: (qmail 13360 invoked from network); 16 May 2000 06:28:24 -0000 From: "Bart Schaefer" Message-Id: <1000516062819.ZM23429@candle.brasslantern.com> Date: Tue, 16 May 2000 06:28:18 +0000 X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Styles that aren't :completion:* ... MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii I notice that the nslookup function uses a context of ':nslookup', whereas assorted zftp components use ":zftp$curcontext". Yet incremental-complete-word uses ":completion:incremental${curcontext#*:}" and similarly insert-and-predict uses ":completion:predict${curcontext#*:}". So these functions actually strip off part of the context and replace it. What's the idiom supposed to be, again? Here's the specific reason that I ask: I'm thinking of adding some more styles to predict-on/off and to the functions they bind to keystrokes. For example, there's a comment in delete-backward-and-predict to the effect that some people might prefer that it call predict-off. That seems like an ideal thing to control with a style, but it feels funny to use a style that starts with ":completion:" because no completion is happening during delete-backward-and-predict. Similarly I was thinking of adding a "verbose" style to predict-on, to have it call "zle -M" when prediction goes into effect. That's called directly from a keystroke. What's the context? -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com