Comment 13 for bug 703775

I built the latest emacs 23, which I believe has the patches you mentioned applied and things do indeed appear to be fixed. I'm running

GNU Emacs 23.2.92.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.22.0) of 2011-01-23 on puma revision 100403, thought it looks like the patch may have been applied in revision 100392.

I also tried a fresh build of current emacs trunk and that too appears to be fixed. The version I am using is

GNU Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.22.0) of 2011-01-23 on puma revision 102847, though I believe the fix was put in in revision 102941.

Note that I had to do considerable re-engineering of my emacs environment to enable running both 23 and 24, plus I've now given up using pre-packaged distribution sources in favor of direct git/bzr sources. This is something I planned to do for a while - the current issue just raised it up the priority path. However, due to all the changes, I've not yet got 100% confidence that everything is working as it should, so it would be good if others can also confirm that this problem no longer exists. Would probably be good to have confirmation on the Windows platform as well.

Tim