On Nov 14, 2007 1:41 PM, Don Dwiggins <[EMAIL PROTECTED]> wrote: > It doesn't need a file; here's a procedure that will recreate it: > - Open a new text file, set the mode to Python. > - Type "def foo(bar):", then newline, then "pass". > - Move the cursor back to just after the colon, press Enter. I get an > empty line with the cursor in the first column.
Aha! I see it, but strangely only on windows. GTK seems fine. Thanks for showing me how to duplicate the problem. > Good news! I think I've found the cause of the traceback problem on > exit: after you do either of the above procedures, exit peppy by using > the close box on the window. It seems to be a problem in dealing with a > "dirty" buffer during shutdown. Yep, I see that, too. Thanks. > Finally, here's another little glitch: after opening a new file and > typing into it, hit Ctrl-S -- peppy complains that saving to > "about:untitled" failed. That's a non-obvious artifact of the about: protocol. Because all my file interaction is based on URLs, I've created this pseudo protocol called 'about' that's analogous to the http protocol in that it's read-only. So, loading from an about: url is fine, but you can't save to it. The intent was that Save would be disabled, but Save As wouldn't be, forcing you to choose a new filename. Interestingly, that exposes a missing bit about my action handling: Ctrl-S is disabled in the menubar and toolbar interface, but I don't disable it when you try the keyboard shortcut. I'll have to disable the keyboard shortcut if the menu item is unavailable. Thanks, Rob
