> IMHO it's not fixed that way, maybe just working per chance because of
> (bobp)
It shouldn't, it's one of the possibilities, docstrings appear either at
the start of a function/method, the start of a class or the start of a
module (file). So after going to the beginning of the statement it
should just be at either at the start of def-or-class or at the
beginning of the file.
If there is something wrong with my reasoning please let me know.
> Severals errors inside.
Inside what? If they're in my code please let me know and I will try to
fix it.
> Patch attached should fix it against previous commit.
Andreas Roehler <email address hidden> writes:
> IMHO it's not fixed that way, maybe just working per chance because of
> (bobp)
It shouldn't, it's one of the possibilities, docstrings appear either at
the start of a function/method, the start of a class or the start of a
module (file). So after going to the beginning of the statement it
should just be at either at the start of def-or-class or at the
beginning of the file.
If there is something wrong with my reasoning please let me know.
> Severals errors inside.
Inside what? If they're in my code please let me know and I will try to
fix it.
> Patch attached should fix it against previous commit.
The patch broke all python font locking for me.