From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5278 invoked by alias); 4 Nov 2017 10:42:07 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 41985 Received: (qmail 13626 invoked by uid 1010); 4 Nov 2017 10:42:07 -0000 X-Qmail-Scanner-Diagnostics: from 195.159.176.226 by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(195.159.176.226):SA:0(-1.1/5.0):. Processed in 1.100847 secs); 04 Nov 2017 10:42:07 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Envelope-From: gcszd-zsh-workers@m.gmane.org X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | X-Injected-Via-Gmane: http://gmane.org/ To: zsh-workers@zsh.org From: Yuri D'Elia Subject: Re: Changing subword-range according to current completion context Date: Sat, 04 Nov 2017 11:41:46 +0100 Message-ID: <87tvyatjf9.fsf@wavexx.thregr.org> References: <87h8ubo9zp.fsf@wavexx.thregr.org> <20171103122349.4bf81a1c@pwslap01u.europe.root.pri> <87h8ubbeaq.fsf@wavexx.thregr.org> <171103182233.ZM31076@torch.brasslantern.com> Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@blaine.gmane.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (gnu/linux) Cancel-Lock: sha1:VOlMVJGXY7uM3vRCtNsiuPAqy6Q= On Fri, Nov 03 2017, Bart Schaefer wrote: > Not really, unless the completion function is designed to do so. The > only things that persist from any call of completion to the next are > which completion widget was used and what comprises the previous list > of possible maches, and all that is lost if any other kind of edit or > motion intervenes between calls to completion. I figured this would be the case. Keeping it in sync would be quite hard as well. Well, I'll keep to the the word-context approach for now. Feels barbaric, but does the job. ;)