From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13003 invoked from network); 26 Apr 2001 23:39:26 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 26 Apr 2001 23:39:26 -0000 Received: (qmail 6548 invoked by alias); 26 Apr 2001 23:39:22 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14131 Received: (qmail 6535 invoked from network); 26 Apr 2001 23:39:21 -0000 Date: Thu, 26 Apr 2001 16:38:50 -0700 (PDT) From: Wayne Davison To: Subject: Re: Another keep-prefix problem In-Reply-To: <1010426171819.ZM17731@candle.brasslantern.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 26 Apr 2001, Bart Schaefer wrote: > something like `~foo' or `$foo', but not if it is `~foo/' or > `$foo/bar', unless that suffix itself contains characters eligible > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > for expansion. The default for this style is `true'. Which is what I'm advocating changing. Don't require the variable to be at the start of the word, just look if there are suffix char(s) between the variable and the cursor, and only expand the variable if the cursor is right next to the variable. This is how the old expander works. > Which means, I think, that you would like the default setting of suffix > to be false rather than true, and the default setting of keep-prefix to > be true rather than "changed". No, setting suffix to false would make it expand variables even when suffix chars are present, and that's different than the default with the old expander, so I'd leave suffix set to true by default. I wouldn't mind having keep-prefix set to true by default, but I think that's a separate issue from making "suffix true" work the same as the old expansion code. ..wayne..