From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13863 invoked from network); 24 Feb 1999 05:14:56 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 24 Feb 1999 05:14:56 -0000 Received: (qmail 28499 invoked by alias); 24 Feb 1999 05:14:34 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5493 Received: (qmail 28492 invoked from network); 24 Feb 1999 05:14:32 -0000 X-Authentication-Warning: c-bart.amazon.com: schaefer set sender to schaefer@tiny.zanshin.com using -f From: Bart Schaefer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14035.35324.873263.193885@c-bart.amazon.com> Date: Tue, 23 Feb 1999 21:11:24 -0800 (PST) To: Sven Wischnowsky Cc: zsh-workers@sunsite.auc.dk Subject: Re: Problem with completion matching control In-Reply-To: <199902231004.LAA24080@beta.informatik.hu-berlin.de> References: <199902231004.LAA24080@beta.informatik.hu-berlin.de> X-Mailer: VM 6.65a under Emacs 20.3.5.1 Reply-To: Bart Schaefer Sven Wischnowsky writes: > > +/* This says what of the state the line is in when completion is started * > + * came from a previous completion. If the FC_LINE bit is set, the * > + * string was inserted. If FC_INWORD is set, the last completion moved * > + * the cursor into the word although it was at the end of it when the * > + * last completion was invoked. * > + * This is used to detect if the string should be taken as an exact * > + * match (see do_ambiguous()) and if the cursor has to be moved to the * > + * end of the word before generating the completions. */ Is that really good enough? Can't the cursor sometimes move from one place in the middle of a word, to some other place in the middle of the same word, depending on exactly what matches are generated? Particularly in the case (ahem) of a case-insensitive matcher?