Re: Programs that don't do X primary selection right

[prev] [thread] [next] [lurker] [Date index for 2004/10/08]

From: Daniel Pittman
Subject: Re: Programs that don't do X primary selection right
Date: 13:26 on 08 Oct 2004
On 8 Oct 2004, Aaron Crane wrote:
> Zack Weinberg writes:

[...]

> Oh, there's way more than that to hate in GNU Emacs's selection handling.
> The most insane bit is that M-Backspace (the obvious and natural way of
> deleting the word to the left of point) 

...to the right of point, out of the box, which is a case for hate all
on it's own.  

I moved from XEmacs to GNU Emacs recently and while it was mostly a good
thing, boy does Emacs build up some hate for some of those key binding
choices.

> actually steals the PRIMARY selection. This is because Emacs has an
> incredibly half-baked idea that the PRIMARY selection should be
> unified with the top of the kill-ring. This doesn't work. For example,
> even with transient-mark mode, selecting a region doesn't assert the
> PRIMARY selection. No, you have to M-w (the equivalent of menu-item
> Copy) to do that. Duh.

This is one area that XEmacs got right for ever.  They just worked the
way an X application should work ... until recently.  Then they made it
work the way GNU Emacs does, because it was ... something.   

Stupider, I guess, since that seems to have been the line of the day.

> Now, Emacs is programmable, so in theory you can fix all of this.  In
> practice, however, it's not quite good enough. 

If you had any notes on that, I would love to get my hands on them.  

Almost, but not quite, enough hate to go back to XEmacs and the random
corruption of piped command content.

           Daniel
-- 
It is disconcerting to reflect on the number of students we have flunked in
chemistry for not knowing what we later found to be untrue.
        -- quoted by Robert L. Weber's, _Science With a Smile_, 1992
There's stuff above here

Generated at 18:01 on 11 Oct 2004 by mariachi 0.52