GNU bug report logs - #6774
Cut and paste with C-w/mouse-2 not working?

Previous Next

Full log

View this message in rfc822 format

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Kenichi Handa <handa <at> m17n.org>
Cc: cyd <at> stupidchicken.com, jan.h.d <at> swipnet.se, 6774 <at> debbugs.gnu.org, angelo.graziosi <at> alice.it
Subject: bug#6774: Cut and paste with C-w/mouse-2 not working?
Date: Thu, 12 Aug 2010 18:09:28 +0200

>> Putting it in set_point_both would be much worse than on
>> post-command-hook (set-point-both is a very low-level function,
>> triggered in many more cases than just moving the cursor).
> If a test to check if we have to newly own the PRIMARY
> selection is trivial, there should be no problem.

And what do we do with the result of the check?  This function too
low-level to be able to perform the "set PRIMARY" from there.

> Another candidate for checking that is somewher near here in
> command_loop_1 () (around line 1818).

>     finalize:

>       if (current_buffer == prev_buffer
> 	  && last_point_position != PT
> 	  && NILP (Vdisable_point_adjustment)
> 	  && NILP (Vglobal_disable_point_adjustment))
> 	{

> This place is similar to post-command-hook, but we can avoid
> unnecessary Lisp calls in many cases.

Yes, that's like post-command-hook.
I'm more worried about the semantics than about the performance impact.
Doing the "set PRIMARY" from C-w and friends is much easier and robust.
Doing it in S-right is OK as well.  Doing it in forward-char is not and
doing it for `right' (by rebinding it to a new command) doesn't sound
too attractive.


        Stefan

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.