From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19551 invoked from network); 11 Jan 2000 19:14:58 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 11 Jan 2000 19:14:58 -0000 Received: (qmail 2856 invoked by alias); 11 Jan 2000 19:14:51 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9294 Received: (qmail 2849 invoked from network); 11 Jan 2000 19:14:50 -0000 Date: Tue, 11 Jan 2000 14:14:34 -0500 From: Clint Adams To: zsh-workers@sunsite.auc.dk Subject: completion with midword tildes Message-ID: <20000111141434.A7223@dman.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0i In dev-14 and the latest jaist CVS snapshot, at least, complete will not complete a word containing a tilde if the tilde is specified. It will, however, do so if a backslash is specified. This happens whether or not EXTENDED_GLOB is set. That is to say % mkdir a~b % cd a --> cd a\~b % cd a~ --> cd a~ % cd a\ --> cd a\~b % cd a\~ --> cd a\~b Some older behavior used to allow % cd a~ --> cd a\~b Is the old behavior undesirable? Particularly when EXTENDED_GLOB is unset, I would expect a~ to complete.