On 2004-12-17 19:22:15 -0500, Thomas Dickey wrote: > On Sat, 18 Dec 2004, Vincent Lefevre wrote: > >When I tried with the latest Debian version, neither of these > >conditions were satisfied (a click shouldn't be regarded as > >starting a selection). So, the bug is still there. > > It's been documented that way for (hmm) 15 years (man xterm): > > The default bindings in the VT102 window are: > > ~Meta <Btn1Down>:select-start() \n\ > ~Meta <Btn1Motion>:select-extend() \n\ > Meta <Btn2Down>:clear-saved-lines() \n\ > ~Ctrl ~Meta <Btn2Up>:insert-selection(PRIMARY, CUT_BUFFER0) > \n\ > > Likewise, it's always possible to change those settings in your resource > file. They're _default_ values.
How should I change them? Does select-extend() work without a select-start() first? > >Also, if the screen is redrawn (e.g. in Mutt, when entering or > >quitting the pager, or in screen, when switching windows), the > >primary selection shouldn't be lost (for instance, xterm should > >put it in a safe place). > > I cannot imagine where it might, since there's always the possiblity > of making a new primary selection. Which (old or new) would be the > correct one? The primary selection should be kept as long as a new selection isn't started (from xterm or another application). -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / SPACES project at LORIA
