From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4392 invoked by alias); 18 Jul 2015 11:55:54 -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: 35816 Received: (qmail 21707 invoked from network); 18 Jul 2015 11:55:50 -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, SPF_HELO_PASS autolearn=ham autolearn_force=no version=3.4.0 X-Injected-Via-Gmane: http://gmane.org/ To: zsh-workers@zsh.org From: Yuri D'Elia Subject: Re: bracketed paste Date: Sat, 18 Jul 2015 13:55:32 +0200 Message-ID: References: <7277.1437023995@thecus.kiddle.eu> <14646.1437186782@thecus.kiddle.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: adsl-ull-109-221.46-151.net24.it User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.0 In-Reply-To: <14646.1437186782@thecus.kiddle.eu> On 18/07/15 04:33, Oliver Kiddle wrote: > My concern is the average user that doesn't configure this. At the > moment people are used to pasted newlines being accepted. If with 5.0.9, > they paste a single line command including a trailing newline, there is > no visible clue to tell them that things have changed: the cursor sits > at the beginning of the next line and the user wonders for a few seconds > why their command is taking so long. > > Like Bart, I'd rather the text is not altered. Sometimes I really want > it verbatim and I can't write a widget to unalter it. Stripping just a > single final newline wouldn't bother me greatly, however and it would > mostly solve to concern I described above. There may be other solutions. I agree here, I also wouldn't want text munging by default. > Anyway, I'm not sure that a style achieves much because it isn't hard > to write a custom widget and a widget is more flexible. The trick of > using a prefix key also means you can have a selection: raw, quoted, > whitespace removed, ${(Z.C.)var} for comment removal etc. I'm still not sure if I can catch the prefix argument when using the new widget (?)