Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Pasting with OSC 52 (for e.g. terminal-based editors) #9479

Open
alexrp opened this issue Mar 13, 2021 · 5 comments
Open

Feature request: Pasting with OSC 52 (for e.g. terminal-based editors) #9479

alexrp opened this issue Mar 13, 2021 · 5 comments
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Help Wanted We encourage anyone to jump in on these. Issue-Task It's a feature request, but it doesn't really need a major design. Product-Terminal The new Windows Terminal.
Milestone

Comments

@alexrp
Copy link

alexrp commented Mar 13, 2021

Related: #2946, #5823

It seems like a decision was made not to support pasting due to security concerns. This is understandable of course, but considering there are editors (such as micro) that actually use this functionality, it's also a bit disappointing.

Perhaps a middle ground would be to have the support but require the user to opt in in Windows Terminal settings?

FWIW, > help copypaste in micro gives this useful info:

* Kitty: supported, but only writing is enabled by default. To enable
  reading, add `read-primary` and `read-clipboard` to the
  `clipboard_control` option.

* iTerm2: only copying (writing to clipboard) is supported. Must be enabled in
  `Preferences->General-> Selection->Applications in terminal may access clipboard`.
  You can use Command-v to paste.

* `st`: supported.

* `rxvt-unicode`: not natively supported, but there is a Perl extension
   [here](http://anti.teamidiot.de/static/nei/*/Code/urxvt/).

* `xterm`: supported, but disabled by default. It can be enabled by putting
   the following in `.Xresources` or `.Xdefaults`:
   `XTerm*disallowedWindowOps: 20,21,SetXprop`.

* `gnome-terminal`: does not support OSC 52.
@alexrp alexrp added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 13, 2021
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 13, 2021
@zadjii-msft
Copy link
Member

Well, there sure does seem like a lot of precedent for a setting that enables this behavior, when it's disabled by default. I can dig that. "Applications in terminal may access clipboard" sounds good to me, but we'll need to find something more succinct than that for the actual setting.

I'm thinking that this should be a per-profile, control-level setting.

Thanks!

@zadjii-msft zadjii-msft added Area-Settings Issues related to settings and customizability, for console or terminal Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Help Wanted We encourage anyone to jump in on these. Issue-Task It's a feature request, but it doesn't really need a major design. Product-Terminal The new Windows Terminal. and removed Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. labels Mar 15, 2021
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Mar 15, 2021
@zadjii-msft zadjii-msft added this to the Terminal Backlog milestone Mar 15, 2021
@DHowett DHowett removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Mar 15, 2021
@thiagowfx
Copy link

Also related: microsoft/vscode#104138

@zadjii-msft zadjii-msft modified the milestones: Terminal Backlog, Backlog Jan 4, 2022
@rsprabery

This comment has been minimized.

@rsprabery
Copy link

This would be great. +1.

Copying text from tmux via OSC 52 is a common workflow and muscle memory always leaves me surprised when I paste something I didn't didn't just copy via tmux.

Wasn't sure where to upvote as it looks like linked bugs were closed.

@zadjii-msft
Copy link
Member

Wasn't sure where to upvote as it looks like linked bugs were closed.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Help Wanted We encourage anyone to jump in on these. Issue-Task It's a feature request, but it doesn't really need a major design. Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

5 participants