zsh-users
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-users@zsh.org
Subject: Re: Shift-Insert overwrites ZLE CUTBUFFER
Date: Thu, 27 Oct 2016 12:59:07 +0000	[thread overview]
Message-ID: <20161027125907.GA20586@fujitsu.shahaf.local2> (raw)
In-Reply-To: <20161027004500.GA12759__18780.7835791775$1477529337$gmane$org@fujitsu.shahaf.local2>

Daniel Shahaf wrote on Thu, Oct 27, 2016 at 00:45:00 +0000:
> Bart Schaefer wrote on Wed, Oct 26, 2016 at 16:51:38 -0700:
> > On Oct 27, 12:12am, lolilolicon wrote:
> > } This doesn't seem to be documented, so I think it's OK to change it.
> > 
> > Good point that it should be documented.
> >
> 
> The following documents the incumbent killring behaviour, and rearranges
> text to clarify that a numeric argument is ignored when a positional
> argument is present.

Alternative patch after feedback by Bart.

diff --git a/Doc/Zsh/zle.yo b/Doc/Zsh/zle.yo
index 726e973..e82c12d 100644
--- a/Doc/Zsh/zle.yo
+++ b/Doc/Zsh/zle.yo
@@ -2176,10 +2176,13 @@ item(tt(bracketed-paste))(
 This widget is invoked when text is pasted to the terminal emulator. It
 is not intended to be bound to actual keys but instead to the special
 sequence generated by the terminal emulator when text is pasted.
+The pasted text is inserted to the buffer and placed in the cutbuffer.
 If a numeric argument is given, shell quoting will be applied to the
-pasted text before it is inserted. When called from a widget function,
-an argument can be given to specify a variable to which pasted text is
-assigned.
+pasted text before it is inserted.
+
+When called from a widget function as `tt(bracketed-paste) var(name)`, the
+pasted text is assigned to the variable var(name) and no other processing is
+done.
 
 See also the tt(zle_bracketed_paste) parameter.
 )


  parent reply	other threads:[~2016-10-27 13:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25 12:46 lolilolicon
2016-10-25 16:12 ` Bart Schaefer
2016-10-25 16:28   ` lolilolicon
2016-10-26 16:01     ` Bart Schaefer
2016-10-26 16:12       ` lolilolicon
2016-10-26 23:51         ` Bart Schaefer
2016-10-27 19:56           ` Greg Klanderman
2016-10-27 20:35             ` Bart Schaefer
2016-10-31 15:56               ` Oliver Kiddle
2016-10-31 16:16                 ` Peter Stephenson
     [not found]               ` <43312.1477929414__19178.7032563754$1477929872$gmane$org@hydra.kiddle.eu>
2016-11-01 17:03                 ` Daniel Shahaf
     [not found]                 ` <20161101170328.GA24091__43513.8293811635$1478019914$gmane$org@fujitsu.shahaf.local2>
2016-11-03 19:45                   ` Daniel Shahaf
     [not found]         ` <161026165138.ZM12130__24043.0697137073$1477525984$gmane$org@torch.brasslantern.com>
2016-10-27  0:45           ` Daniel Shahaf
     [not found]           ` <20161027004500.GA12759__18780.7835791775$1477529337$gmane$org@fujitsu.shahaf.local2>
2016-10-27 12:59             ` Daniel Shahaf [this message]
2016-10-26 22:05       ` Mikael Magnusson
2016-10-26 23:59         ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161027125907.GA20586@fujitsu.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).