On 10/24/07, Josiah Carlson <[EMAIL PROTECTED]> wrote: > On 10/24/07, Rob McMullen <[EMAIL PROTECTED]> wrote: > > but if I replace it with another one I have lying around, pype > > starts (but I must have left something out because I don't actually > > get any syntax highlighting). But doesn't give me the error. > > Do you restart PyPE? Do you switch to some other syntax highlighting, > then switch back to Python?
Yep, as I mentioned, I just replaced the stc-styles.rc.cfg from the pype distribution with one from peppy back when I was using the Boa styling scheme like PyPE does. (I use Editra's styling now, btw.) Anyway, I found the problem. This missing '#' in the stc-styles.rc.cfg distributed with PyPE-2.8.8 caused the error, so you might want to update your source distribution. $ diff stc-styles.rc.cfg ../tmp/stc-styles.rc.cfg 22c22 < style.python.014=fore:#ffffff,back:000000 --- > style.python.014=fore:#ffffff,back:#000000 > > The one thing I might > > try to enhance is returning to the base intention level after closing > > a continuation line, e.g.: > > > > self.blah(arg1, arg2, > > arg3, arg4) > > ^ > > > > where pype places the cursor at the ^ instead of under the 's' after > > hitting return after the close paren. > > That is known and expected behavior ;), where it errs on the side of > doing less work. Technically, in order to be correct in all cases, > one may need to check all previous lines. And for the size of source > files I typically end up editing (and sometimes the way I edit), going > as far back as necessary can cause a noticeable delay (something that > I hate when I'm writing software, which is why I don't use Wing IDE, > and some others). Yeah, there's always some corner case that would cause unacceptable delay. I figure that emacs does it (mostly) correctly, and if emacs can do it in elisp without me noticing, the same ought to be possible in python. :) Heck, emacs didn't have noticeable delay back when I was running on [insert-dating-myself-hardware-reference-here], so to do it emacsishly correct should be reasonable. Rob
