From: jpw@pobox.com (John Paul Wallington)
Subject: Re: Debugging byte compiled files
Date: Sat, 04 Mar 2006 23:33:34 +0000 [thread overview]
Message-ID: <87irqteqep.fsf@thunk.shootybangbang.com> (raw)
In-Reply-To: mailman.602.1141491264.5838.help-gnu-emacs@gnu.org
"Phillip Lord" <Phillip.Lord@newcastle.ac.uk> writes:
> I've recently found a bug in my own pabbrev.el package. It's taken
> me so long because it only occurs when the file is byte compiled
> and I don't routinely byte compile my own packages.
>
> I think that the problem is coming from this macro...
>
> (defmacro pabbrev-save-buffer-modified-p (&rest body)
[...]
Does the `defmacro' form occur before its use within your library ?
next parent reply other threads:[~2006-03-04 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.602.1141491264.5838.help-gnu-emacs@gnu.org>
2006-03-04 23:33 ` John Paul Wallington [this message]
2006-03-06 8:51 ` Debugging byte compiled files Stefan Monnier
2006-03-07 18:51 Phillip Lord
-- strict thread matches above, loose matches on Subject: below --
2006-03-07 18:48 Phillip Lord
2006-03-07 19:16 ` John Paul Wallington
2006-03-04 16:54 Phillip Lord
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=87irqteqep.fsf@thunk.shootybangbang.com \
--to=jpw@pobox.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.
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).