all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Scott Barnett <scott.n.barnett@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Edebug-x visual extensions to Edebug
Date: Tue, 12 Mar 2013 15:10:23 +0100	[thread overview]
Message-ID: <87y5dsyai8.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <CA+RXH5x_OfGkbwG4CqMbp_PZCgrHm+UUemH9goNpqBg9SbW2qg@mail.gmail.com> (Scott Barnett's message of "Tue, 12 Mar 2013 22:56:13 +1100")

Scott Barnett <scott.n.barnett@gmail.com> writes:

Hi!

> I made a small extension to Edebug that highlights breakpoints, shows
> a list of currently instrumented functions and provides a couple of
> other extras to make Edebug easier for me to use.

Sounds great!

> If this is something that should be included please let me know of the
> next steps.

Except for the copyright assignment, there are at least two things I can
spot while glancing at the code that hinder its inclusion in emacs
proper.  The first one is that you shouldn't require cl, and the second
is the dependency to the external dash package.

With emacs 24 you can use `cl-restructuring-bind' and `cl-find-if'
instead of the unprefixed versions.

Instead of dash's `-each' you can use `mapc', instead of `-map' you can
use `mapcar', instead of `-remove' you can use `cl-remove-if', and
instead of `-contains?' you can use `member'.

Bye,
Tassilo



  parent reply	other threads:[~2013-03-12 14:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 11:56 Edebug-x visual extensions to Edebug Scott Barnett
2013-03-12 13:53 ` Xue Fuqiao
2013-03-12 14:10 ` Tassilo Horn [this message]
2013-03-12 14:22   ` Xue Fuqiao
2013-03-14  6:47     ` Scott Barnett
2013-03-14  7:03       ` Tassilo Horn
2013-03-14 13:15         ` Stefan Monnier
2013-03-14 13:16       ` Stefan Monnier

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=87y5dsyai8.fsf@thinkpad.tsdh.de \
    --to=tsdh@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=scott.n.barnett@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.