From: spam@fisher.forestry.uga.edu (Chris Fonnesbeck)
Subject: Re: python-mode problems in emacs (pdb)
Date: 10 Mar 2004 13:09:33 -0800 [thread overview]
Message-ID: <c3835e5f.0403101309.25974a43@posting.google.com> (raw)
In-Reply-To: wRo3c.212$KJ.8949@nnrp1.ozemail.com.au
"Peter Milliken" <peterm@resmed.com.au> wrote in message news:<wRo3c.212$KJ.8949@nnrp1.ozemail.com.au>...
> What makes you think this is an Emacs problem? (I assume that you believe it
> to be an Emacs problem since you are posting here instead of
> comp.lang.python - your statement is not exactly definitive :-))
>
> pdb.set_trace() works fine for me in my Emacs (21.3.1 on Windoze) sessions.
>
> Peter
Well, I assumed it was a python-mode.el problem. I am running it on
OSX, and emacs is still a bit embryonic on that platform, which I why
I am assuming emacs is the culprit. I dont care whodunnit, I just want
to fix it.
Thanks,
cjf
prev parent reply other threads:[~2004-03-10 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 16:15 python-mode problems in emacs (pdb) Chris Fonnesbeck
2004-03-09 19:24 ` Peter Milliken
2004-03-10 21:09 ` Chris Fonnesbeck [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c3835e5f.0403101309.25974a43@posting.google.com \
--to=spam@fisher.forestry.uga.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).