On Mon, Aug 4, 2014 at 2:02 AM, Ken Brown <kbr...@cornell.edu> wrote: > That does seem to be the problem, since I can reproduce the bug starting > with the 2014-07-14 snapshot. More precisely, I can reproduce it using > emacs-nox (which is what the OP was using according to his cygcheck output) > but not using emacs-X11 or emacs-w32. Thanks for your help in resolving this. I am indeed using emacs-nox. Do you think emacs-x11 or emacs-w32 would be a good alternative to work round the problem in the short term?
Peter -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
