I sent the following to
aquama...@aquamacs.org 10 days ago. I didn't get a response (automated or otherwise), and I wasn't sure if that just means no one had time to look at it yet, or if something went wrong, so I am posting it here as well. Please forgive me if you had to see it twice. Thanks!
Thank you all for your work on Aquamacs. It is by far the most pleasant way to write code on the Mac...
I do experience one issue with Aquamacs
becoming unresponsive and needing to force-quit. It is related to
visiting a file (via C-x C-f) that is already open, in the mode where
each buffer opens in a new frame. It can be reproduced consistently as
follows:
1. Help->Diagnose and Report Bug->Try Aquamacs without customizations
2. Options->Show tabs (disable it)
3. Options->Open buffers in new frames (enable it)
4. C-x C-f to visit any file "o1". It opens in the frame that previously held the empty scratch buffer, as expected
5. C-x C-f to visit any file "o2". It opens in a new frame as expected.
6. In the "o2" frame, Command-w to close the newly opened frame for "o2"
7. Back in the "o1" frame, C-x C-f to visit "o2" again. It opens in a new frame again as expected.
8.
In the "o2" frame, C-x C-f and visit "o1". Here is where the issue
occurs. It should switch back to the "o1" frame, but rather it opens a
new third frame, which is displaying "o2" rather than "o1", and then
becomes unresponsive.
The
above steps make it happen every time as far as I can tell. I see this
both with the latest nightly build, and with the latest release 3.4.
Thanks for looking into it, and please let me know if I can provide
additional details.