From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16409 invoked by alias); 31 Aug 2016 11:20:41 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 21828 Received: (qmail 26509 invoked from network); 31 Aug 2016 11:20:41 -0000 X-Qmail-Scanner-Diagnostics: from mailout1.w1.samsung.com 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(210.118.77.11):SA:0(-1.5/5.0):. Processed in 0.424615 secs); 31 Aug 2016 11:20:41 -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.5 required=5.0 tests=RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: p.stephenson@samsung.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts) X-AuditID: cbfec7f5-f792e6d0000013f5-cb-57c6bb24dd06 Date: Wed, 31 Aug 2016 12:10:25 +0100 From: Peter Stephenson To: covici@ccs.covici.com, zsh-users@zsh.org Subject: Re: history substring search too aggressive sometimes Message-id: <20160831121025.14c1c869@pwslap01u.europe.root.pri> In-reply-to: References: <20160830204905.16d9f703@ntlworld.com> <20160831100851.5ce89562@pwslap01u.europe.root.pri> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBLMWRmVeSWpSXmKPExsVy+t/xK7oqu4+FG3xaomKxtEPSYsfJlYwO TB49O/4yeqw6+IEpgCmKyyYlNSezLLVI3y6BK+PSxM+MBf/YK/Yv6GFvYFzJ1sXIySEhYCLx cOIDRghbTOLCvfVgcSGBpYwSsyeWQtgNTBIHGiq6GLmA7HOMEl8WrWCCcM4ySpxZPRvI4eBg EVCVmH2+HqSBTcBQYuqm2WBDRQR0JD6s3Qo2VFjATmJ2Wz9YnFfAXmL+7N1MIDangJHE7+nT GSFm3mOUmDdnJzNIgl9AX+Lq309MENfZS8y8cgaqWVDix+R7LCA2s4CWxOZtTawQtrzE5jVv mSGuVpe4cXc3+wRG4VlIWmYhaZmFpGUBI/MqRtHU0uSC4qT0XCO94sTc4tK8dL3k/NxNjJDw /rqDcekxq0OMAhyMSjy8B2YdDRdiTSwrrsw9xCjBwawkwntzx7FwId6UxMqq1KL8+KLSnNTi Q4zSHCxK4rwzd70PERJITyxJzU5NLUgtgskycXBKNTCWz44UUdP31v1ySuxeO+Osr/Pm/+Rp tz6y5cRKQxnBVZXpDU+Mp7/cffvziZ2BX1ftUNk2/3Zq0RVpq9o5rjFHdwb8Pnl23Yudi9LC Tsp4SQalNoWWLnWollKdsi0vocqFTabow3dxztXXxdKlBXuW18t/jzk4q8BHubDQfgNb20EW w6sRQoVKLMUZiYZazEXFiQCqt+/JawIAAA== On Wed, 31 Aug 2016 07:03:58 -0400 John Covici wrote: > Well, I was looking at the options section of the manual, and > although its not perfect yet, disabling menucomplete which was on and > complete_in_word, helped a great deal. Also, I discovered to get a > list of all the options, I had to do > set -o > instead of setopt which I was doing before. Hmm, setopt should show you all non-default options, so if menucomplete was on it should show up. That explains why you're getting the first word inserted. complete_in_word is only applied if the cursor is in the middle of the word when you hit tab, and only at that point. (The standard assumption is you're at the end of the word you're completing, but it should be possible to get it to work anyway.) None of the other options look relevant. Note there are additional extra things going on if you have directory paths as it will complete multiple components, but it didn't sound like that was the issue. pws