[Python-mode] making stack traces clickable in gud.el pdb output.

[m h]

(forgot to reply to list)

On Tue, Jan 19, 2010 at 4:36 PM, Barry Warsaw <barry at python.org> wrote:
> On Jan 19, 2010, at 03:06 PM, m h wrote:
>
>>So just to be explicit about what 'run your code from a shell buffer'.  I tried:
>>
>>1- C-c !
>>2- type `execfile('filename.py')` into python shell
>>3- hit breakpoint/nirvana
>
> Actually, no!  Seriously, run it in a shell buffer. :)
>
> M-x shell RET
> % python filename.py
> hit breakpoint/nirvana
>

I was using M-x ansi-shell....  It worked in M-x shell.  Thanks.

> :)
>
>>Is that how you do it, or is there another way?  It'd be nice not to
>>have to type out part 2.  Right now I have a macro bound to f-11 that
>>re-runs my last pdb command.  I guess M-p (like ctr-p in terminal)
>>works ok too in  that it scrolls through the command histories.
>>
>>So that get's rid of one of my problems (gud/pdb scrolls buffer to
>>top).  Anyway to make it recognize files and make them clickable in
>>the python shell?
>
> "clickable"?  Is that like using that mouse thing?  To paraphrase a wise man,
> "There's no clicking in Emacs!" :)
>

;)  Yeah, I'm trying to avoid that bad habit of 'clicking'.

ok, how about 'hyperlinkable'?  I've got an ack.el extension that
searches for files, in it's buffer you can move the cursor over the
file (with the keyboard!) and hit enter and it will pop you to that
file/linum.

-matt