Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upMore detailed information on paste dialogue #2636
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jpouellet
Feb 15, 2017
Contributor
This is not easy because of how that code in question is obtaining the VM names.
That code is not at all in the call path of the copy/paste operations, it is only watching the files which are produced as a side-effect of the current implementation of copy/paste (done by the gui-daemon).
The source VM name is stored in a file which can be easily observed, the target VM name is not.
Implementing this would require changes elsewhere as well in order to obtain that information.
|
This is not easy because of how that code in question is obtaining the VM names. That code is not at all in the call path of the copy/paste operations, it is only watching the files which are produced as a side-effect of the current implementation of copy/paste (done by the gui-daemon). The source VM name is stored in a file which can be easily observed, the target VM name is not. Implementing this would require changes elsewhere as well in order to obtain that information. |
starfys commentedFeb 15, 2017
•
edited
Edited 1 time
-
starfys
edited Feb 15, 2017 (most recent)
When pasting from the Qubes clipboard, a notification appears that says
Relevant source (line 100)
Could it be changed to include the target VM name just for a bit more reassurance that data is being pasted to the right place?
Possible replacement:
This would provide extra reassurance and be more in line with the notification shown when copying to the Qubes clipboard.