From: Michael Shields <shields@msrl.com>
Subject: Two questions about byte compilation
Date: Sun, 12 Jan 2003 22:27:46 +0000 [thread overview]
Message-ID: <87smvyuhp9.fsf@mulligatwani.msrl.com> (raw)
1. The skip-boring patch I've written tries to add to gnus.art:
(defcustom gnus-article-boring-faces (cons 'gnus-signature-face
gnus-cite-face-list)
[...]
This doesn't byte-compile properly, because gnus-cite-face-list is
undefined. However, I can't (require 'gnus-cite), because
gnus-cite.el has (require 'gnus-art) and the byte-compiler loops
until hitting the recursion limit.
What is the right way to fix this?
2. Why does dgnushack.el wrap an (ignore-errors) around the call to
byte-compile-file? This causes files with errors to silently fail
to compile; then after "make install" you have a mix of old and new
files, with no warning.
--
Shields.
next reply other threads:[~2003-01-12 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 22:27 Michael Shields [this message]
2003-01-12 22:54 ` Lars Magne Ingebrigtsen
2003-01-13 6:27 ` Michael Shields
2003-01-13 16:21 ` kgreiner
2003-01-13 18:29 ` Lars Magne Ingebrigtsen
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=87smvyuhp9.fsf@mulligatwani.msrl.com \
--to=shields@msrl.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 NNTP newsgroup(s).