On Nov 14, 2007 12:11 PM, Don Dwiggins <[EMAIL PROTECTED]> wrote: > - Auto-indentation is working pretty well in Python mode, with one > exception: when the cursor is at the end of an existing "def ..." line, > hitting Enter doesn't indent. It works fine when typing a new one, however.
I've noticed a similar problem, but for me it only happens rarely and I've never been able to duplicate it consistently. Does it always fail for you? If you have a test file shows the problem, would you mind forwarding it to me? > - If I use the Buffers menu to visit a different buffer instead of the > Python one I'm editing, then go back to the Python buffer, the major > mode is set back to Fundamental. (This only happens with an unsaved new > buffer; once I save it to a file, the mode comes back properly after > switching buffers.) Yep, I see that. I should set the default major mode of a new file to the new major mode when its major mode is explicitly set by the user. > - If I close a buffer containing a file, then re-open the file, it gets > put into a buffer with a "<n>" suffix, as though there were still > another buffer around with the file's name. This is minor, but could > get mildly annoying during a long session. I copied this behavior directly from XEmacs. I actually find it a bit annoying myself, so maybe after all the buffers of a particular name are deleted, I'll reset the count to zero. > - On closing peppy, I'm still getting the same traceback I reported > before. (By the way, the shell prompt doesn't return after this; > something's holding the python process open. When I give it a BREAK > signal, the process closes and the prompt comes back -- this also > happened before.) There's a thread that's not getting cleaned up. I put a sys.exit in the code, but because of the exception you're seeing, the sys.exit doesn't get called. The real solution is to find out what's causing that exception (athough after that I need to figure out why that thread doesn't get shut down). > On balance, it's starting to look usable; I'll try it again when I have > to edit a "real" file, and have time to be careful with it. Thanks, I appreciate the bug reports. Rob
