zsh-workers
 help / color / mirror / code / Atom feed
From: Yuri D'Elia <wavexx@thregr.org>
To: zsh-workers@zsh.org
Subject: bracketed paste
Date: Wed, 18 Nov 2015 20:57:14 +0100	[thread overview]
Message-ID: <n2il6q$gb$1@ger.gmane.org> (raw)

If you remember, I sent a patch for urxvt and bracketed paste in Debian
a while ago:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787628

I now realized that we could avoid all the escaping madness if we
re-define what bracketed paste should do for us. I briefly checked and
found no use in the wild of bracketed paste (scanning for the escapes in
google and github).

This made me think what I've written before in the bug report: what if
the terminal just encodes into base64 the block to be pasted? What we'd
need to just is just wait for the end sequence, decode the block, and we
have no other issues with break processing. It would even allow to send
binary content in the way (d&d in the terminal, who-ho!).

Heck, I'll write a patch to xterm myself if I'd need to push this through.


             reply	other threads:[~2015-11-18 20:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 19:57 Yuri D'Elia [this message]
2015-11-19  6:05 ` Bart Schaefer
2015-11-19  9:33   ` Yuri D'Elia
  -- strict thread matches above, loose matches on Subject: below --
2015-07-15 16:51 Yuri D'Elia
2015-07-15 17:33 ` Yuri D'Elia
2015-07-15 18:15   ` Mikael Magnusson
2015-07-15 18:43     ` Yuri D'Elia
2015-07-16  5:19 ` Oliver Kiddle
2015-07-16 14:32   ` Yuri D'Elia
2015-07-18  2:33     ` Oliver Kiddle
2015-07-18 11:55       ` Yuri D'Elia
2015-07-18 17:17       ` Bart Schaefer
2015-07-18 23:28         ` Oliver Kiddle
2015-07-16 20:15   ` Bart Schaefer
2015-07-18 12:05     ` Yuri D'Elia
2015-07-18 18:08       ` Bart Schaefer
2011-11-07 22:31 Oliver Kiddle
2011-11-07 22:42 ` Mikael Magnusson

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='n2il6q$gb$1@ger.gmane.org' \
    --to=wavexx@thregr.org \
    --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).