zsh-workers
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: bracketed paste mode in xterm and urxvt
Date: Wed, 3 Jun 2015 21:42:58 +0100	[thread overview]
Message-ID: <20150603204258.GE4767@chaz.gmail.com> (raw)
In-Reply-To: <27004.1433345491@thecus.kiddle.eu>

2015-06-03 17:31:31 +0200, Oliver Kiddle:
> [ moved to -workers ]
> 
> Yuri D'Elia wrote:
> > On 05/28/2015 10:30 PM, Daniel Hahler wrote:
> > > Apart from that I think that this (bracketed paste mode) should be
> > > included in Zsh's and get maintained this way.  Then it could also be
> > > adjusted for vi-mode.
> > 
> > I do agree that mainlining this would make a lot of sense, even as a
> > setopt. Or at least provide the keymap/functions needed to enable it.
> 
> I've been using bracketed paste for a while now and would also agree.
> The question is in what form to provide it? Note that I posted an
> alternative mechanism in workers/29898. The patch below is a port of
> that to C.
[...]

Also note that where terminals don't filter out control
characters, there's a potential problem in the way ^C is
handled.

zsh disables all signal keys but "intr". If the data to paste
(which is written in one go to the master side of the pty by
the terminal emulator) contains ^C, then a SIGINT will be sent
to zsh and the data from the start  of the paste up to ^C will
not be available for reading (discarded by the line discipline,
at least on Linux).

So any bracketed paste solution cannot be safe unless either ^C
is removed by the terminal emulator (like newer versions of
xterm), or ISIG is disabled in the terminal line-discipline.

So, for a truly safe paste, zsh should probably do the
equivalent of a stty -isig. That can only be done *before* the
paste, so that means isig must be turned off all the time (at
least when bracketed paste is enabled). Not desirable as CTRL-C
comes handy to stop lengthy processes by the shell.

To sum-up, for a safe bracketed paste, you need either:

- terminal emulator to filter out ^[ and ^C

Or if the terminal doesn't filter out ^[ and ^C both:

 - a different paste mode than xterm's \e[200~<to-paste>\e[201~ which
   doesn't work as <to-paste> may contain \e[201~ (something
   like: insert-formatted("\033[202~%S~%s",
   CLIPBOARD,PRIMARY,CUT_BUFFER0) would do).
 - zsh to disable isig.

Maybe a better approach would be to query the X selection for
instance with xclip/xsel where available. That can also be
integrated with the zsh kill ring. I once implemented a PoC
around that idea together with mouse integration

https://github.com/stephane-chazelas/misc-scripts/blob/master/mouse.zsh

-- 
Stephane


  reply	other threads:[~2015-06-03 20:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTikh_-+L2W5=Yfu7h7iAe5CcpP6fxw@mail.gmail.com>
     [not found] ` <CAFOazAOfk=Sq-smkMGzJKO4b7jMb_1_m4vXXn8twoVA2wV55YA@mail.gmail.com>
     [not found]   ` <55677AF5.50709@thequod.de>
     [not found]     ` <mk9dc0$p0$1@ger.gmane.org>
     [not found]       ` <CABZhJg_5p8BLbq82s_wVtsPdD5hVtk-cPg6fNxzbSs4Vg00SOw@mail.gmail.com>
     [not found]         ` <mkmjfu$3h0$1@ger.gmane.org>
     [not found]           ` <CAHYJk3T3dVdN5qDMecPAH_ALLBYNntW0QVdPMh50Lo_ULeWP6w__21110.9288772152$1433333265$gmane$org@mail.gmail.com>
2015-06-03 12:43             ` Stephane Chazelas
2015-06-03 15:31       ` Oliver Kiddle
2015-06-03 20:42         ` Stephane Chazelas [this message]
2015-06-03 23:48           ` Oliver Kiddle
2015-06-04  7:15             ` Stephane Chazelas
2015-06-05 10:49         ` Yuri D'Elia
2015-06-05 13:40           ` Oliver Kiddle
2015-06-05 14:35             ` Yuri D'Elia
2015-06-10  0:28               ` Oliver Kiddle
2015-06-10  4:38                 ` Bart Schaefer
2015-06-15 22:11                   ` Oliver Kiddle
2015-06-15 23:09                     ` Mikael Magnusson
2015-06-16  0:20                     ` Bart Schaefer
2015-06-16 17:12                       ` Oliver Kiddle
2015-06-16 20:26                         ` Bart Schaefer
2015-06-17 10:45                           ` Oliver Kiddle
2015-06-17 15:04                             ` Bart Schaefer
2015-06-10  9:44                 ` Yuri D'Elia

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=20150603204258.GE4767@chaz.gmail.com \
    --to=stephane.chazelas@gmail.com \
    --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).