On Fri, Dec 14, 2012 at 11:00:22AM -0500, Brandon Allbery wrote:
> biggest failing. I submit for your consideration copy/paste (one of the
> most frequent user issues in the xmonad community): not only are there
> multiple incompatible copy/paste systems, but you cannot make xterm behave
> in the same way that other programs do without source hacks.
I know of only one cut/paste method in X11, and it is quite compatible with
Really? You've never tried to copy/paste text between something using the instant-copy PRIMARY and the pasteboard-based CLIPBOARD selections? Take a look at the herd of hacks to deal with them (by means of a mostly-obsolete *third* mechanism, cut buffers! I'm just grateful nobody ever made significant use of SECONDARY to make things even weirder): xcutsel, autocutsel, etc.
> And, of
> course, it's quite impossible to make X11 programs on OS X behave like
> native programs; there are always small but annoying oddities at best, and
> often complete dissonance.
Again, you're not talking about X11. Nor are you talking about OS X's
So perhaps I should have expanded on that, since I incorrectly assumed that one might be able to generalize.
You have different and sometimes incompatible behaviors between:
Raw Xlib programs
Xt+Xaw programs
Xt+Motif programs (and Motif-inspired; ask FreeBSD users about cvsup's GUI sometime)
Gtk+/Gnome programs
Qt/KDE programs (these two *almost* manage to behave similarly, but not quite)
Tk programs
(thank g*d nobody uses Open Look any more... although people do occasionally get to discover how XView-based stuff differs yet again. And differs yet again from Xt/Xt+ programs from AT&T's version)
And that's in an all-X11 ecosystem!
--