On Fri, May 1, 2009 at 4:50 PM, Andreas Roehler <span dir="ltr"><<a href="mailto:andreas.roehler@online.de">andreas.roehler@online.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">Barry Warsaw wrote:<br>
> On Apr 30, 2009, at 4:07 PM, Andreas Roehler wrote:<br>
><br>
>> I'll send you two screenshots offlist. Please feel<br>
>> free to forward them to interested persons, just didn't<br>
>> want to publish my path at the list.<br>
>><br>
>> 20090428_pdbtrack3.png displays pdbtrack opened second<br>
>> windows, cursor displayed at line 4 "import"<br>
>><br>
>> With 20090428_pdbtrack4.png you see shell-output<br>
>> from line 8, but cursor in second window still is at line 4.<br>
>><br>
>> Always get "Traceback cue not found"<br>
>><br>
>> Cause seems var `py-pdbtrack-stack-entry-regexp'.<br>
>><br>
>> That doesn't happen, if pdb.set_trace() is inside the<br>
>> python-file.<br>
>><br>
>> Did someone else remark this?<br>
><br>
> Hi Andreas,<br>
><br>
> I haven't heard this one before, but perhaps it's because of the ipython<br>
> prompt?<br>
<br>
</div></div>Maybe. As shows message in first screenshot #3, pdbtrack indicates line 4 correctly.<br>
Its not brocken completely.<br>
</blockquote><div><br>i'm having some difficulties tracking your descriptions of the situation, andreas, but i think
you (and barry) are right that the problem is failure to recognize, rather than pdbtrack not being activated (as you seemed to initially be suggesting).<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Its a question of regexp, which doesn't recognise/accept the result, delivered by `block'.<br>
</blockquote><div><br>i don't understand what you mean by "delivered by 'block'"<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Already tried to change the regexp or even simply eliminate that checking step, but not<br>
found a solution.<br>
</blockquote><div> <br>the match may be necessary to parse the traceback, and for other reasons.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hhm. Could you give me an example, how you run script activating pdbtrace, reaching<br>
the standard (pdb) prompt from Emacs?<br>
</blockquote><div><br>what do you mean by "reaching the standard (pdb) prompt from Emacs"?? perhaps you're talking about the python interaction buffer that python-mode provides? i believe, but am not certain, that pdbtrack watches the output in any comint buffer, including the python interaction buffer. i can check this kind of thing, but need to understand better what you're saying before investigating.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Only get it from shell.<br>
</blockquote><div><br>one thing i can suggest that you do is copy the text from the emacs buffer that pdbtrack should recognize but doesn't, and send that excerpt to us. i know that's in the pictures, but it's easier for you to send us the text than it is for us to type it accurately from the pictures.-) preferably you would also send an excerpt that is similar but is successfuly recognized.<br>
<br>i will try to find time to examine it, and see if i can identify what is happening and what should be happening...<br>-- <br>ken<br><a href="http://myriadicity.net">http://myriadicity.net</a><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks<br>
<font color="#888888"><br>
Andreas<br>
</font><div><div></div><div class="h5"><br>
<br>
I think pdbtrack expects (by default) the standard (pdb) prompt.<br>
><br>
> -Barry<br>
</div></div></blockquote></div><br>