From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25981 invoked by alias); 26 Oct 2016 18:11:46 -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: 22031 Received: (qmail 5602 invoked from network); 26 Oct 2016 18:11:46 -0000 X-Qmail-Scanner-Diagnostics: from mail-lf0-f43.google.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(209.85.215.43):SA:0(0.0/5.0):. Processed in 0.338425 secs); 26 Oct 2016 18:11:46 -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=0.0 required=5.0 tests=FREEMAIL_FROM,SPF_PASS, T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: lolilolicon@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.215.43 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Ez8Hup2ql+ZE+OmWenoJS/ExRspUB+KugzKPWt8esB4=; b=vf9pZvL5Jrqmyoegk3USBhVjZW5AaP3h2HDK7TquxK5CaiQIttRvGjd2rQNEPRT0vH cdKoT8Kp8dggtmsmEix7JaLfEBnwVlBcC9zcfNfBS2/0WIKVISYcp7mheW0J3Bz2zAfl pFKgjBpCtVxAh2PsU7Jda4zAuN6IWIXDMwG7JStlH4yvWR+6ToxwH4s+wriQu9zGMaMx UKuMpOPIBViO+nXOW2Wvd+SmDkHMgpQxV4PnEbjxmX/EEO2Wkim5KUW/OOCyEsAixYSO cmcDodYeDwr1uXgH2fhhCDtKSzBdtvxvd/+WDx1CLYCRK0mNCmRt+pZnhDufZvEwqcVm KsVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Ez8Hup2ql+ZE+OmWenoJS/ExRspUB+KugzKPWt8esB4=; b=cAF1gqsMIUZW+sVmZ2w1w3xFdAZJZ5i+sOMwDSd2y5jOjB/5C/1cy6LGc1nB49Ky9d XXYZASdQXXF91Jyv2VgyI8KX9s0SBSTvx3vhhEAgT9rr4JbCN+oa2T8TZuY/SnLH7COM uN12T8/tImqBOvLjeG3s+cPz9F5yj31mA6mieD9JZB+pKSq088k9oBs3JoQp+LtYZesJ gANS+s/JarbzfP8WFf5mdHi2zrJKbl87iCVNLL0azd/yGfQRvo8TuWj3FhXe948mrw3o V/iMQm018kbDGqsIqboCSPZ23U8bJUsBRwmB1n+AkI4JEOsYu3DdfMWhx0Haf9lvPMQX 6bhw== X-Gm-Message-State: ABUngvf5W75qchhjkLmgnlaEmiPhznlpi093SOWDPY83S4D6RRJQ0ssyFgNkSek5/W5Ot/2+6TNNQJ/fuYyGVA== X-Received: by 10.25.40.74 with SMTP id o71mr2522839lfo.183.1477498361581; Wed, 26 Oct 2016 09:12:41 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <161026090133.ZM11120@torch.brasslantern.com> References: <161025091249.ZM7232@torch.brasslantern.com> <161026090133.ZM11120@torch.brasslantern.com> From: lolilolicon Date: Thu, 27 Oct 2016 00:12:41 +0800 Message-ID: Subject: Re: Shift-Insert overwrites ZLE CUTBUFFER To: Bart Schaefer Cc: zsh-users@zsh.org Content-Type: text/plain; charset=UTF-8 On Thu, Oct 27, 2016 at 12:01 AM, Bart Schaefer wrote: > What I mean is that it's not easy to do from shell code. In the source > code obviously the implementation is deliberately pushing the kill ring, > so it wouldn't be technically difficult to *not* do so, but that would > mean reversing an earlier design decision. I assumed the kill ring was used for implementation convenience. If this was a deliberate design decision, I don't understand how this is desirable to the user. This doesn't seem to be documented, so I think it's OK to change it. > > Something like this sort of works: > > my-bracketed-paste { > zle .bracketed-paste "$@" && { > local pasted=$CUTBUFFER > # Swap the top two killed items to fake out ^Y > CUTBUFFER=$killring[1] > killring[1]=$pasted > } > } > zle -N bracketed-paste my-bracketed-paste > > But I wouldn't have called that an "easy way". Nice, thanks for showing me! > > Various other approaches involving saving/restoring CUTBUFFER and killring > are also possible.