From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19675 invoked by alias); 29 Jul 2015 15:30:36 -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: 20358 Received: (qmail 5372 invoked from network); 29 Jul 2015 15:30:34 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=fpgh+66jZWAeNa8dleYfe+Q/F0wmLOWz5LuEioeXjkw=; b=YPq8VH00d8oub8LthPpD3r0S6LaH2wfLFrlcGMFFQ3k48p0mu3xYcRk1Gxhp1RJ4uH OvdMK6DQthmKt6YEkWK3hwEjPAorHYmr3Uw643Difmh49DL+C5FcwTD2fCxR2sxYb1Yz sfWhxVgz3XLrYq79jjlImBX5xsitS2ZxfsxEuDU60sKBXd6snUMsclHvd6G+fQuGnfKU ePqVt4YvNkQH67lAtFwvzmDqU+mQvkheXPUUTH3sgOC4wbx4SdQhek2Xs8fEK35weH7L NRs2oT9aEAKk/bZQ3l/BNDwL0vOWg6mkQh+9YOB2v6EwsOpUs1qRXPntVJd+ZpdebUMk MSlQ== X-Gm-Message-State: ALoCoQmbfOquLFTQ3guvimSeihUxgmEJD5AjhRyzpCFIcL8qMavZHvKtVyYhieTsicuJj8DjAHGS X-Received: by 10.182.176.36 with SMTP id cf4mr42241124obc.40.1438183831506; Wed, 29 Jul 2015 08:30:31 -0700 (PDT) From: Bart Schaefer Message-Id: <150729083027.ZM10252@torch.brasslantern.com> Date: Wed, 29 Jul 2015 08:30:27 -0700 In-Reply-To: Comments: In reply to Mikael Magnusson "Re: Vimode problem (key press dropping)" (Jul 29, 2:35pm) References: <5d9984411ba10dee4321a408e2763317@riseup.net> <9361.1438161965@thecus.kiddle.eu> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh Users Subject: Re: Vimode problem (key press dropping) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jul 29, 2:35pm, Mikael Magnusson wrote: } } I always felt like how it should work if we get the string "abc", is } first abc is looked up and we find it isn't bound to anything, the a } gets treated as a separate input string, then we look up bc instead, } etc. The problem with that is that if you have an unbound function key on your keyboard, striking it will cause unpredictable effects when the leading ESC is ignored and the rest of the sequence begins to be interpreted as individual characters. } What we do now is just discard the whole string as "undefined-key". Which is correct if the whole sequence came from a single keystroke; the real difficulty is determining whether that happened.