xwinclip shouldn't monitor the primary selection

[Harold L Hunt II]

uribarri_u@tsm.es wrote:

> I think that xwinclip shouldn't monitor the primary selection because:
> a) The primary selection has user feedback. When an X application loses the
> primary selection, usually clears the selection, so you can't delete, cut,
> copy or whatever you want to do.
> b) The primary selection doesn't behave like the windows clipboard, so
> windows users get confused.
> 
> On the other hand, the clipboard selection doesn't usually have user
> feedback and behaves like the windows clipboard: you must request the cut
> or copy operation explicitly.
> 
> What do you think?
> 

I think that somebody mentions this about once every other week without 
searching the mailing list archives first.  I have written at least 15 
detailed descriptions of why making xwinclip/-clipboard work "properly" 
is HARD.

Harold