From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1251 invoked by alias); 26 Oct 2016 17:10:07 -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: 22030 Received: (qmail 14715 invoked from network); 26 Oct 2016 17:10:07 -0000 X-Qmail-Scanner-Diagnostics: from mail-yw0-f179.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.161.179):SA:0(0.0/5.0):. Processed in 0.760802 secs); 26 Oct 2016 17:10: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=0.0 required=5.0 tests=T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at brasslantern.com does not designate permitted sender hosts) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=BejyujLikcFqaVqs6XHxTL4NgahRvng+9OKFzCP6a1A=; b=ma0D0ty8optqjOIcoW1zG1CguSFgRkySJEq+C69Zg+JmR7I8CPqt06/z8p/cHswLlq ev/xcoj9eqVGHIt+Kt5p9bISXOIhGR9uC3qOr5zJiE4lvaP3M2P+oIJPXF5/PgxxVaD5 Tor3tljqWBpFmD1NEV4naNl4Fee83fhXcwi0qCAZ4n30CgMwL0g5JUl7UCJUu2HN8MLL 9JnzTZHvOKuweaCT99g2YtyTdMAEqbs4nBW24LHi7AgANVUPsE0iAmWYrXKLORik1PPp o2oT5watdzZC6iBOGCLMk83EVxZy6/55RDOMjh0iINtgIAMB5g9UvAWBD8RlO2XpBdOB IrAA== 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; bh=BejyujLikcFqaVqs6XHxTL4NgahRvng+9OKFzCP6a1A=; b=V518oRylFDXQSZNgJUmb8wkMuc/YfEyYXpnKHiYqXtCk0uJatvTf44wPMFA1QaDKSh T6EHc74K0hd3sbYMbq1arP7QqNObEBnSpAfxzhI1sXc0ciJDPsw08O0ptOG+rIN85nO7 dTgyb9GIix1+8dHJcJnUE14trT5LXl6+WgYYL6Urww7nt6Sm3rqBIRYArON1I+EL1U0Z GtFm3Gq2B7AuecGmSbE42KrYju6Tp7LptksH8Icw+cahYohPRjXiaMN+/mNxv9m6n17c C/7g7Im2R7OmmkZxLieUxgoc/yCgjS1ya5hSLVmp1LWEGWCdz2+XnBiwXMx+pvNffgYW Q/fw== X-Gm-Message-State: ABUngvfLkLsf3Gm1my4CAjcM/HKcYht68UZkmf0BD18y8QQ3vVwrseSOy4k//6kMHmZmxQ== X-Received: by 10.13.206.131 with SMTP id q125mr2305856ywd.161.1477497680714; Wed, 26 Oct 2016 09:01:20 -0700 (PDT) From: Bart Schaefer Message-Id: <161026090133.ZM11120@torch.brasslantern.com> Date: Wed, 26 Oct 2016 09:01:33 -0700 In-Reply-To: Comments: In reply to lolilolicon "Re: Shift-Insert overwrites ZLE CUTBUFFER" (Oct 26, 12:28am) References: <161025091249.ZM7232@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: Shift-Insert overwrites ZLE CUTBUFFER MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Oct 26, 12:28am, lolilolicon wrote: } Subject: Re: Shift-Insert overwrites ZLE CUTBUFFER } } On Wed, Oct 26, 2016 at 12:12 AM, Bart Schaefer } wrote: } > There's currently no easy way to change the cutbuffer behavior without } > disabling the rest of the bracketed-paste behavior. } } That's a shame. } Is it technically difficult to do? Would there be an issue if zsh just } popped the killring automatically? 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. 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". Various other approaches involving saving/restoring CUTBUFFER and killring are also possible.