On 10/24/07, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> On 10/23/07, Rob McMullen <[EMAIL PROTECTED]> wrote:
> > I know you do most of your work on Windows, but have you seen this
> > bizarro error before? I can't get PyPE to turn on the Python lexer
> > because it's having a problem with Red():
>
> Upgrading Ubuntu (6.06) to wxPython 2.8.6.0 unicode from the wxwidgets
> apt repository and running PyPE seems to work fine for me. Do you
> have any references to 'red' in your stc-styles.rc.cfg?
It's definitely something to do with the Boa styling, but I can't
pinpoint it. There's nothing obviously wrong with the stc-styles
file, 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.
> Unless you
> have changed the contents of yours, it shouldn't have any (it's the
> same one I use all the time). I know it's total blasphemy, but have
> you tried the source version on Windows and/or the Windows binaries?
It was the default stc-styles file, so I don't know why it's messing
up on mine. I might upgrade to the latest svn of wxPython and see if
it's still is a problem.
But, I was able to fire up the ol' windows box and try it out. It's
working fine on Windows, and I see that your indent-on-return does the
right thing in lists, dicts, nested structures, and within
continuation lines, so I'll take a look at it. 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.
Rob
