zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: bracketed paste - FAQ update
Date: Sat, 15 Aug 2015 23:34:33 +0000	[thread overview]
Message-ID: <20150815233433.GG1952@tarsus.local2> (raw)
In-Reply-To: <20150716234205.GH2032@tarsus.local2>

Daniel Shahaf wrote on Thu, Jul 16, 2015 at 23:42:05 +0000:
> Question 3.24 "3.24. What's wrong with cut and paste on my xterm?" has:
> 
>   myeit() When the shell is waiting for input, and you paste in a chunk of
>      text consisting of more than one complete set of commands.
> [...]
> Maybe update this to reflect the new 5.0.9 behaviour?

Haven't caught up with my inbox yet, but in the meantime:

diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo
index a9cc0a6..e6d5094 100644
--- a/Etc/FAQ.yo
+++ b/Etc/FAQ.yo
@@ -1702,11 +1702,17 @@ sect(What's wrong with cut and paste on my xterm?)
      already active, and needs to be turned off when the first command is
      executed.  The shell doesn't even know if the remaining text is input
      to a command or for the shell, so there's simply nothing it can do.
+
      However, if you have problems you can trick it: type `tt({)' on a line
      by itself, then paste the input, then type `tt(})' on a line by
      itself.  The shell will not execute anything until the final brace is
      read; all input is read as continuation lines (this may require the
      fixes referred to above in order to be reliable).
+
+     As of 5.0.9, this trick is not necessary on terminal emulators that
+     support the em(bracketed paste) feature (this includes most modern
+     terminal emulators).  See the description of tt($zle_bracketed_paste)
+     in the tt(zshparam) manual page for details.
   )
 
 


      reply	other threads:[~2015-08-15 23:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 23:42 Daniel Shahaf
2015-08-15 23:34 ` Daniel Shahaf [this message]

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=20150815233433.GG1952@tarsus.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-workers@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).