Comment 8 for bug 250359

I agree that Ctrl+C is unlikely to be bound to copy, for the reason you gave.
It is a little worrying that someone unfamiliar with Ctrl+C ⇒ SIGINT could
interrupt changes, but then this argument could equally apply to a sudo
command at any terminal. (To head off a possible argument: Synaptic’s
embedded terminal appears only if one twiddles the Details option, but I don’t
think that this is a justification for its being for advanced users only and
therefore acceptably dangerous, because this twiddling is easily
discoverable.)

I agree that there should be an easily recognisable method for copying text (a
button or context menu, as you say), but I don’t think that this precludes a
fairly standard keyboard shortcut from being implemented as well. As I said,
I imagine that a keyboard shortcut would be easier to implement than a GUI
element (there are no usability questions as to where to place a GUI button,
if nothing else), so that could be a justification for its being in a separate
report that could be implemented first.

I’m not sure that having two reports is in this case creating extra work for
developers, since both are fairly simple, well defined bugs or feature
requests that could usefully be attacked sequentially.

I think that the descriptions of the two reports describe the problems quite
well, and it would be hard to put both issues succinctly into one description,
so even if both difficulties are solved by the same Synaptic update, I think
it is worth describing them separately.

They are indeed requesting essentially the same end (easier copying), but by
different means.

While I don’t know that I disagree strongly, I shall unlink the two reports
for now for the reasons I gave above. If you or anyone else does feel
strongly, the reports can be re-linked!