Bug 907 - copying to clipboard doesn't if I previously copy text from emacs
Summary: copying to clipboard doesn't if I previously copy text from emacs
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2011-09-19 13:06 UTC by Jeffrey Stedfast
Modified: 2011-09-30 06:01 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Jeffrey Stedfast 2011-09-19 13:06:40 UTC
I don't know if this happens all the time or not, but if I copy some text from emacs and paste into MD and then try to copy some text inside MD and paste into another area in the same file in MD, the paste command pastes the contents I had copied from Emacs and not what should have been overwritten when I did a copy inside MD.

I can continue to copy new text buffers from emacs and paste them into MD, but cannot copy text from MD to paste inside MD.
Comment 1 Jeffrey Stedfast 2011-09-19 14:48:03 UTC
It doesn't seem to have to be emacs, I just reproduced it after having copied some exception spew from a terminal to paste into colloquy and then going to MD and trying to copy&paste some code to another location in the file.

I can't get MD to overwrite the text I had copied from the terminal window.

It doesn't matter if I use the Edit menu or use Command+C to copy...
Comment 2 Jeffrey Stedfast 2011-09-19 15:06:48 UTC
Turns out Cut (Command+X) doesn't work either. Same if I use it from the menu.

Figured I should double-check that the prefs for the keybindings for those menu items is correct (looking at the shortcut symbols in the menu, they looked right), so opened up MonoDevelop Preferences and went to the keybindings section and sure enough, Copy & Paste are set correctly.

If I try to re-set the copy command to Command+C, when I press Command the command symbol is rendered in the text-entry field but as soon as I hit C, it activates the accelerator for the Cancel button at the bottom of the dialog and the dialog cancels/closes.
Comment 3 Jeffrey Stedfast 2011-09-19 15:13:49 UTC
I just reverted monodevelop to b148c013b023ab26c4aad49d548fe19b93fb97da

and reverted md-addins to 0abc7be573ac7b170c76b2a204c5cfdb464e93f6

now copy/paste works perfectly. So something since those commits broke copy/paste for me.
Comment 4 Jeffrey Stedfast 2011-09-19 15:34:27 UTC
This is the patch that breaks copy&paste for me:

Comment 5 Mikayla Hutchinson [MSFT] 2011-09-19 18:42:00 UTC
Hm, that doesn't make sense. That code's completely unrelated.

Also, the GTK theme we use on Mac doesn't have button mnemonics...
Comment 6 Mike Krüger 2011-09-20 03:00:24 UTC
I agree with michael hutchinson - that's completly unrelated to the cut & paste system. When this revert fixes a cut & paste bug it's exposing a bug somewhere else.
Comment 7 Mike Krüger 2011-09-21 04:25:11 UTC
Any news on that. What do we now with that ?

(copy&paste always worked for me - with & without 8e2966e652d09ded25760953b89de4ea8656f5e9)
Comment 8 Mikayla Hutchinson [MSFT] 2011-09-21 07:22:28 UTC
Yeah, I'd like my icons back :)

If I had to hazard a guess, I'd say that the non-fatal errors that Jeff was seeing caused by the icon fetching code were allowing gdk or cocoa to corrupt memory. However, I was unable to reproduce those, so I'll need help from Jeff to hunt them down.
Comment 9 Jeffrey Stedfast 2011-09-21 11:58:13 UTC
how are you guys building MonoDevelop where you aren't seeing the icon problems or the c&p problems?

I'm building an env with bockbuild, then sourcing the md-dev-env file and then cd'ing into the monodevelop directory and doing:

./configure --profile=mac && make && cd ../md-addins && ./configure --profile=mac && make && make run
Comment 10 Mike Krüger 2011-09-30 00:41:13 UTC
Closing that one.

Are the icons back ?!?
Comment 11 Mikayla Hutchinson [MSFT] 2011-09-30 06:01:03 UTC
I brought the icons back, because I couldn't reproduce this problem, and I added some checks that should prevent the errors that Jeff was seeing in the other related bug (though I couldn't reproduce those either).