After playing around with this some more, it seems to be related to the location from which I open the files. For various reasons, I have a B: drive that is an alias for my C:\Users\bengle directory. The B: drive is created by the following command being executed from a batch file when I log onto Windows:
subst B: %USERPROFILE% (or else: subst B: C:\Users\bengle)
When I open files via the B: drive (as B:\Projects\...) the problem happens. If I open those same files from the C: drive
(as C:\Users\bengle\Projects\...), then the problem does not seem to happen, or at least not yet.
This problem just started happening in Beta 5 because I normally do all of my work through the B: drive.
All you have to do, is open a file, and then click around on the window (or double click) a few times in various places, and all of the sudden, whoosh, the window turns into a command log. Sometimes, if you have multiple windows open, the file will just close, or the window will magically turn into a buffer for some completely different file.
Also, I am wondering if this might be language-specific. I can reproduce the problem easily with C++ files, but with batch files and plain text files, it doesn't seem to be happening.
Is there anything I can do to collect problem documentation for you?