I've followed this thread from the beginning. I'm impressed by the time, dedication and thoroughness that the two of you put into it.
Thank you David and Eli. - Ray (Emacs user only since 2000) PS, the usual apologies for the backwards message quoting apply. ----------------------------------- Date: Thu, 19 Nov 2015 19:46:30 -0600 From: David Vanderschel <[email protected]> To: "[email protected]" <[email protected]> I upgraded my little laptop to Windows 10 Version 1511 (analogous to an SP1) this week, and the problem no longer exists. This is consistent with what I had been saying all along, namely that the new wrong behavior was due to a bug in Windows 10. Furthermore, the good news is that it has been fixed; and, in spite of the length of the thread resulting from my original post, there is no need to worry about it anymore. Regards, David V. -snip-
