Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Gnus 5.11 in Emacs CVS
Date: Thu, 15 Jan 2004 01:46:14 +0100	[thread overview]
Message-ID: <m3vfnekpih.fsf@defun.localdomain> (raw)
In-Reply-To: <iluu12z6og3.fsf@latte.josefsson.org> (Simon Josefsson's message of "Wed, 14 Jan 2004 07:20:44 +0100")

Simon Josefsson <jas@extundo.com> writes:

> 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.

Regarding those warnings: Is there a reason that we often do

  (eval-when-compile
     (require 'foo))

rather than[1]

  (autoload 'foo-open "foo")

The later would remove the "might not be defined at runtime" warnings.


[1] or autoload cookies, if it's used in many files.




  reply	other threads:[~2004-01-15  0:46 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
2004-01-15  0:46               ` Jesper Harder [this message]
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=m3vfnekpih.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    /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).