Add configuration for whether selection remains or clears on copy #7728

Closed
opened 2026-01-31 01:11:19 +00:00 by claunia · 3 comments
Owner

Originally created by @vadimkantorov on GitHub (Apr 27, 2020).

Originally assigned to: @carlos-zamora on GitHub.

Selection disappears after copy (on latest release):

If I remember well, this is behavior of cmd.exe and is not how Gnome Terminal / wsltty / Notepad / any Windows app works. If you work in multiple tabs and copy things in several rounds. It is quite useful to see what was copied / where selection was previously.

Given that https://github.com/microsoft/terminal/issues/4477 is fixed, it is now trivial to discard selection when one does not want it. So keeping selection even after copy now is practical.

After selection, before copy:
image

After copy (Ctrl+Shift+C):
image

Now if I switched windows / tabs / did some other clipboard manipulations, I no longer have a way to remember / recall what I already copied last time from this lovely Python disclaimer.

Originally created by @vadimkantorov on GitHub (Apr 27, 2020). Originally assigned to: @carlos-zamora on GitHub. Selection disappears after copy (on latest release): If I remember well, this is behavior of cmd.exe and is not how Gnome Terminal / wsltty / Notepad / any Windows app works. If you work in multiple tabs and copy things in several rounds. It is quite useful to see what was copied / where selection was previously. Given that https://github.com/microsoft/terminal/issues/4477 is fixed, it is now trivial to discard selection when one does not want it. So keeping selection even after copy now is practical. After selection, before copy: ![image](https://user-images.githubusercontent.com/1041752/80354342-e522c100-8876-11ea-8c00-ef579b0a283c.png) After copy (Ctrl+Shift+C): ![image](https://user-images.githubusercontent.com/1041752/80354386-f66bcd80-8876-11ea-9ca6-15bfb8a976a0.png) Now if I switched windows / tabs / did some other clipboard manipulations, I no longer have a way to remember / recall what I already copied last time from this lovely Python disclaimer.
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 29, 2020):

Marked up as a p3 task for terminal backlog. Thanks!

@DHowett-MSFT commented on GitHub (Apr 29, 2020): Marked up as a p3 task for terminal backlog. Thanks!
Author
Owner

@carlos-zamora commented on GitHub (May 13, 2020):

After scanning most of our repo, I think this is actually a /dup of #3884. Linking and updating that one. Refer to that one for updates and discussion.

@carlos-zamora commented on GitHub (May 13, 2020): After scanning most of our repo, I think this is actually a /dup of #3884. Linking and updating that one. Refer to that one for updates and discussion.
Author
Owner

@ghost commented on GitHub (May 13, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (May 13, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7728