From: Simon Josefsson <jas@extundo.com>
Subject: Re: Gnus 5.11 in Emacs CVS
Date: Wed, 14 Jan 2004 07:20:44 +0100 [thread overview]
Message-ID: <iluu12z6og3.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3u12z9klj.fsf@defun.localdomain> (Jesper Harder's message of "Wed, 14 Jan 2004 06:15:36 +0100")
Jesper Harder <harder@ifa.au.dk> writes:
> [1] In some ways I think we're doing ourselves a disservice with the
> elaborate compilation scheme. With cvs Emacs (at least) most of
> it should be unnecessary because `(if (fboundp' kills the
> warnings.
We could drop lpath/dgnushack in favor of automake's elisp support. I
did that locally a few weeks ago, without any obvious problem. It
generated a bunch of new byte compiler warnings, which we should fix.
I didn't handle the XEmacs specific part, but they could easily be
hidden in an automake condition, enabled by --with-xemacs or
emacs/xemacs guessing logic.
Opinions? I guess Lars will have to decide, since there are several
rules in the makefiles that seem to be used by him only.
next prev parent reply other threads:[~2004-01-14 6:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 11:01 Per Abrahamsen
2004-01-05 21:18 ` Steve Youngs
2004-01-05 22:01 ` Reiner Steib
2004-01-06 5:08 ` Lars Magne Ingebrigtsen
2004-01-08 17:58 ` Reiner Steib
2004-01-13 22:22 ` Reiner Steib
2004-01-13 23:08 ` Jesper Harder
2004-01-14 5:15 ` Jesper Harder
2004-01-14 6:20 ` Simon Josefsson [this message]
2004-01-15 0:46 ` Jesper Harder
2004-01-15 2:30 ` Simon Josefsson
2004-01-14 14:18 ` Reiner Steib
2004-01-22 7:43 ` Jesper Harder
2004-01-22 15:17 ` Reiner Steib
2004-02-15 0:03 ` Miles Bader
2004-02-15 0:18 ` Miles Bader
2004-04-14 20:24 ` Reiner Steib
2004-04-15 0:37 ` Miles Bader
2004-05-12 10:17 ` Reiner Steib
2004-01-05 22:12 ` Xavier Maillard
2004-01-06 13:46 ` Per Abrahamsen
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=iluu12z6og3.fsf@latte.josefsson.org \
--to=jas@extundo.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).