Re: [cvs] bug when using pc-selection-mode/transient-mark-mode

[Karl Chen <quarl@hkn.eecs.berkeley.edu>]

So I added your debugging suggestion but before I could use it, by luck I
discovered what was causing this mark dactivation bug.

It happens whenever I copy or paste text. `interprogram-cut-function' is
x-select-text, which calls x-set-selection, which calls
x-own-selection-internal.

Summary of how to reproduce this bug:
M-x pc-selection-mode
M-: (x-own-selection-internal 'PRIMARY "quack")
C-x C-f bigfile
hold down S-down.

Without the x-own-selection-internal, the selection would be from the
start of the file to whatever line you were on. After any clipboard copy
operation, the selection will at random times get deactivated and the
selection won't be ever more than a couple lines.

I don't see at all what could cause this behavior in xselect.c, nor do I
see any relevant changes recently in xselect.c. I'll check out old
snapshots of emacs to see if they have this behavior.

-- 
Karl Chen / quarl@quarl.org


On Wed, 18 Sep 2002, Richard Stallman wrote:

>     I can't figure out how exactly to reproduce the problem because it doesn't
>     manifest as soon as I start emacs. I've tried going through all the
>     motions I usually do (invoking different autloads through buffers/files,
>     compiling, autorevert, etc.) in case something autoloads globally.  All I
>     can say (I know this isn't much use, sorry) is that after having edited
>     for a while the selection-deactivation behavior starts.
>
> In that case, I think only you are in a position to debug it.
> You could put (if debugging (debug)) into the code in simple.el
> that deactivates the mark, and set debugging to t when you want
> to debug.
>
> (Save all your buffers before you start debugging this way.)
>