Hi, today I worked with the command line tool 'qvm-open-in-vm' and realised that its behaviour is quite similar to qvm-open/qvm-copy.
The way I understand it is: There used to be qvm-copy-to-vm/qvm-move-to-vm which would take the name of the destination vm as first parameter and a file path as the second parameter. At some point (I believe it was with the release of Qubes 4.0) these tools have been deprecated in favour of qvm-move/qvm-copy, which now take only one parameter and interactively ask the user for the destination VM. qvm-open-in-vm still works like the older tools, that is, it takes two parameters (VM name + file name or URL to be opened), but then still shows the GUI prompt where the user needs to pick the destination VM. I am not overly familiar with Qubes inter-VM communication but from my point of view, qvm-open-in-vm should be deprecated as well and replaced by a similarly working qvm-open tool. What do you think? Please let me know if this mail should rather be addressed to qubes-devel. Regards, Phil -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6df43db9-8c7d-7458-1f1b-41c2d885b597%40digitrace.de.
signature.asc
Description: OpenPGP digital signature
