unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christoph <cschol2112@googlemail.com>
To: Dave Love <fx@gnu.org>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	Stefan Monnier <monnier@IRO.UMontreal.CA>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Current state of python.el in the Emacs trunk
Date: Wed, 23 Feb 2011 23:13:38 -0700	[thread overview]
Message-ID: <861v2y9cz1.fsf@gmail.com> (raw)
In-Reply-To: <87oc66ky5s.fsf@liv.ac.uk> (Dave Love's message of "Mon, 21 Feb 2011 00:51:27 +0000")

Dave Love <fx@gnu.org> writes:

> I'm not sure what fixes you mean.  I've just maintained a separate
> version.

I was volunteering in case you were willing to let us incorporate any
fixes and improvements you made to your separate mode into the trunk but
couldnt or didnt want to do it yourself. The commentary of your file
says that certain bugs have been fixed, iirc.

> That stuff simply shouldn't be there, which is why it originally
> wasn't.

That's what I am currently working on cleaning up. This is mainly to
provide a cleaner base for the integration of functionality from
Fabian's new mode.

> It appears all the world's Python, so it doesn't matter if it causes
> global problems and more-or-less excludes similar things for other
> interpreters as far as I remember.  (I implemented a gud-minor-mode, of
> course, but it required changes to gud.el and I didn't keep up with
> Emacs.  I think the general facility was less code than the
> Python-specific version.)

I am unclear as to how gud-minor-mode would be better, since I am not
familiar with that mode at all. However, I remember reading in some old
thread where somebody made the point that Python's way of debugging
doesn't lend itself well to using a gud-minor-mode. I might have to go
back and reread that thread again.

Christoph



  reply	other threads:[~2011-02-24  6:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27  4:32 Current state of python.el in the Emacs trunk Christoph
2011-01-27 18:35 ` Stefan Monnier
2011-01-28  0:23   ` Christoph
2011-02-15 20:07   ` Dave Love
2011-02-15 20:13     ` Chong Yidong
2011-02-15 22:33       ` Stefan Monnier
2011-02-16  3:05         ` Christoph
2011-02-16  4:32           ` Stefan Monnier
2011-02-21  0:49             ` Dave Love
2011-02-16  7:07           ` Fabian Ezequiel Gallina
2011-02-21  0:52             ` Dave Love
2011-02-21  0:51           ` Dave Love
2011-02-24  6:13             ` Christoph [this message]
2011-03-29  4:58               ` ken manheimer
2011-03-29 14:03                 ` Stefan Monnier
2011-03-29 15:34                   ` Fabian Ezequiel Gallina
2011-03-30  2:12                   ` Christoph Scholtes
2011-02-21  0:48         ` Dave Love
2011-02-21  2:10           ` Stephen J. Turnbull
2011-02-21  2:25           ` Stephen J. Turnbull
2011-02-21 22:25           ` Stefan Monnier
2011-02-21  0:48       ` Dave Love
  -- strict thread matches above, loose matches on Subject: below --
2011-01-27  9:33 Андрей Парамонов

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=861v2y9cz1.fsf@gmail.com \
    --to=cschol2112@googlemail.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=fx@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).