From: Ken Raeburn <raeburn@cygnus.com>
Cc: "(ding) GNUS Mailing List" <ding@ifi.uio.no>
Subject: ELP (was Re: speedup in gnus-sum (B m command))
Date: 29 Oct 1996 22:35:47 -0500 [thread overview]
Message-ID: <tx1www95dkc.fsf@cygnus.com> (raw)
In-Reply-To: David Moore's message of 26 Oct 1996 20:04:05 -0800
David Moore <dmoore@UCSD.EDU> writes:
> I'm also currently putzing around with changes to elp which
> allow it to do full profiling (ie, call tree information) which might
> help with gnus's strange oo-backend call traces. Before I write all of
> this, has anyone on the list done something similar? (I've already
> fixed elp to properly handle autoloads and keysequences making it
> "safer" to use on gnus.)
Great! I recently asked the same question in bug-gnu-emacs, and the
answer appears to be "no", but I don't have the time to do the actual
work right now.
Some bits of information I got from the maintainer:
* the correct email address for correspondence is tools-help@python.org,
not the address used by M-x elp-submit-bug-report
* the maintainer is "Barry A. Warsaw" <bwarsaw@anthem.cnri.reston.va.us>
but you should use the above email address, and he's got "little
incentive (or time)" to work on this idea, but would welcome the
contribution of code
* a newer version of elp than either emacs-19.34 or xemacs has,
version 2.37, is available, at http://www.python.org/ftp/emacs/;
it has mostly bug fixes, some small new features; it's been
submitted to rms too for future releases
Ken
prev parent reply other threads:[~1996-10-30 3:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-27 4:04 speedup in gnus-sum (B m command) David Moore
1996-10-30 3:35 ` Ken Raeburn [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tx1www95dkc.fsf@cygnus.com \
--to=raeburn@cygnus.com \
--cc=ding@ifi.uio.no \
/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 NNTP newsgroup(s).