From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11336 invoked by alias); 10 Nov 2016 16:27:13 -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: 39910 Received: (qmail 11600 invoked from network); 10 Nov 2016 16:27:13 -0000 X-Qmail-Scanner-Diagnostics: from nm21-vm5.bullet.mail.ir2.yahoo.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(212.82.97.2):SA:0(0.0/5.0):. Processed in 0.153509 secs); 10 Nov 2016 16:27:13 -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: okiddle@yahoo.co.uk X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.mail.yahoo.com designates 212.82.97.2 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048; t=1478794907; bh=V/XbC+br1hCGs9iwTmfFBpCqstFk+UK55RhUwXh+C9Y=; h=In-reply-to:From:References:To:Subject:Date:From:Subject; b=OddLt1lA2gFxMiWCmGnikjXiCFsejTCvUyQdwNajD4qOZbTHBay4p9wFCkPEyC6ardBejj3oCAMjrEs05YKZlAMS55DooCKcokVQXxCzHk//qHUTLHCnMlqAybUHoKQMGJoywV+wY/uAennh9CINw8BqAF+JF2CQzSwQ3/lx2m6imfPG422k/1MqoB13cPfAcYOi4xw96NAdlNfFRdHRaSzyP952bHHpZODD3PzIa1tTtBxSKlr4gVCOweCwzxkf3/HFqIOoUnR9B37+KEXMSgFXMXLAINgVFgtaT9UpaXmY3fNV2ey2183FMDqqxVk0OSRvClpCBRkmraGFwYMM9Q== X-Yahoo-Newman-Id: 117649.46868.bm@smtp145.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 8Plz47IVM1kUKuKuOCaxWEwSLySV.VG_o6FDOcxg1Nfhk6R Kn.NwJOXd6xao2gBFIhOfvTA7TY.pW_nHqXFK0tVoUAEqFdA65teG2HS39Mc 9Qml9nCjeHA1obqZxFZnHeL3QVcczBh1WwrhWOjHlVVVVIzFWTdK_p9TOSXd d2IiZtowon3B4saJJ2_F8daSCRYLlogwj6PIO95FRCtns_tEKZvGm1TxHG0G jg12Pa7HN2RCB5w07q2cyuxdGw5k4rTGPEGbp7zmWr6DlMxOpHiLlotZXb0H mlLF54jZqcIqpiEhlLeSqV6.xlMSBJdGDP6XeD0hS0GTfz_C53wKq7BwKN5B ecWotW2b2g66MIOagRGDedqscFiryD0B4tB23.ilpkE7nkULeAvtp.ADZLJF Adb.U0UuJHeCERLoU8AIeAjcKccndWe6y511jm0_bdCxM4Yxu1r68sXK0U1H gN.OKi31Ds0kOxD0zM8YP6goCZyNNXLnU8dCJaFCRtAV.1OT02V2joGV_KEZ 541H2ujGE2Ivg6maGSWPOqVe3itZgSZE7mKpNgAM- X-Yahoo-SMTP: opAkk_CswBAce_kJ3nIPlH80cJI- In-reply-to: <161109092745.ZM2477@torch.brasslantern.com> From: Oliver Kiddle References: <161025091249.ZM7232@torch.brasslantern.com> <161026090133.ZM11120@torch.brasslantern.com> <161026165138.ZM12130@torch.brasslantern.com> <87h97x36sa.fsf@lwm.klanderman.net> <161027133523.ZM15655@torch.brasslantern.com> <43312.1477929414@hydra.kiddle.eu> <20161031161605.23af1751@pwslap01u.europe.root.pri> <161109092745.ZM2477@torch.brasslantern.com> To: zsh-workers@zsh.org Subject: Re: Shift-Insert overwrites ZLE CUTBUFFER MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4445.1478794906.1@hydra.kiddle.eu> Date: Thu, 10 Nov 2016 17:21:46 +0100 Message-ID: <4446.1478794906@hydra.kiddle.eu> Bart wrote: > > On Oct 31, 4:56pm, Oliver Kiddle wrote: > } > } Associating it with the existing cut/paste features at least puts > } it in a logical and memorable place, at least once you're aware of > } the feature. And if you know about things like yank-pop or vi "0 > } then it is not so likely to be bothersome. But I'd be open to > } something better. > > On Oct 31, 4:16pm, Peter Stephenson wrote: > } > } I'm not particularly bothered either way, but $ZLE_PASTED suggest > } itself. A variable isn't an especially convenient place for the text given that it is mostly useful interactively. You can't do anything useful without writing custom shell widgets and if you're going to be writing custom shell widgets, you might just as well write one to wrap bracketed-paste and stuff the text into a variable. > An idea that I just had, spawned in part by Oliver's change to > "print -v" behavior when the target variable is declared as an array: The array would at least then serve as a simple one-liner to disable the use of the CUTBUFFER if it turns out that it bothers a lot of people. I've mostly found the feature useful with an explicit vi buffer and that behaviour is easily preserved while changing the rest. Does emacs perhaps have anything analagous to the vi buffers? (It appears to be a vim thing to call them registers as I've been doing). Would there be any sense in putting it in the kill ring but not in the CUTBUFFER so yank-pop is needed to grab it. Oliver