From: Chong Yidong <cyd@stupidchicken.com>
To: Jeremy Whitlock <jcscoobyrs@gmail.com>
Cc: 5653@debbugs.gnu.org
Subject: bug#5653: 23.1; pdbtrack isn't parsing valid pdb output or creating an interactive debugging buffer (python.el)
Date: Mon, 10 May 2010 16:52:10 -0400 [thread overview]
Message-ID: <87eihj7a4l.fsf@stupidchicken.com> (raw)
In-Reply-To: <0603CEE9-0865-4319-A2B9-88BCC0FFBB0E@gmail.com> (Jeremy Whitlock's message of "Mon, 10 May 2010 11:03:39 -0600")
Jeremy Whitlock <jcscoobyrs@gmail.com> writes:
>> Attached is a patch that fixes this issue. Basically, Python (pdb)
>> is passing strings to Emacs with ^M in them. My patch, attached and
>> pasted in this email just in case, strip the carriage return from the
>> string and after that, pdb starts working as expected. Here is the
>> patch, generated from "git format-patch":
>
>
> There hasn't been any noticeable progress on this based on the issue
> tracker. The intent of this message isn't to bug anyone but I would
> like to know if the patch was usable or if you'd like to suggest
> another approach for fixing this issue. Just let me know.
Sorry, I have not had the time to review the patch. I'll do it as soon
as I can.
next prev parent reply other threads:[~2010-05-10 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 21:09 bug#5653: 23.1; pdbtrack isn't parsing valid pdb output or creating an interactive debugging buffer (python.el) Jeremy Whitlock
2010-02-27 0:22 ` Chong Yidong
2010-03-01 23:46 ` Jeremy Whitlock
2010-04-10 1:11 ` Jeremy Whitlock
2010-04-10 1:30 ` Jeremy Whitlock
2010-05-10 17:03 ` Jeremy Whitlock
2010-05-10 20:52 ` Chong Yidong [this message]
2010-05-10 20:54 ` Jeremy Whitlock
2011-03-29 17:45 ` bug#5653: gud.el / How To fix pdb in Emacs on Mac OS X (solution) Markus Heiser
2011-06-27 21:38 ` Chong Yidong
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=87eihj7a4l.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=5653@debbugs.gnu.org \
--cc=jcscoobyrs@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).