From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8301 invoked by alias); 9 Dec 2010 16:10:49 -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: X-Seq: 28507 Received: (qmail 15241 invoked from network); 9 Dec 2010 16:10:48 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <101209081029.ZM8252@torch.brasslantern.com> Date: Thu, 09 Dec 2010 08:10:29 -0800 X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Vi motion commands and $BUFFER MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Fooling with 33facebook's "dl" complaint, I find "zle .vi-delete" (and any other vi command that must be followed with a motion to set the operating range) appears to fail when used in a wrapper that makes any kind of modification to BUFFER/LBUFFER/RBUFFER. Even saving and restoring CURSOR doesn't help. This doesn't appear to affect the motions themselves, just commands that use getvirange() internally.