unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, emacs-devel@gnu.org
Subject: Re: loaddefs and provide
Date: Tue, 03 Nov 2009 22:58:48 -0500	[thread overview]
Message-ID: <jwvmy337xpo.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <o0bpjjugol.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 03 Nov 2009 22:12:10 -0500")

>> * calendar/calendar.el (cal-loaddefs):
>> * calendar/diary-lib.el (diary-loaddefs):
>> * calendar/holidays.el (hol-loaddefs):
>> * eshell/esh-module.el (esh-groups):
>> * mh/mh-e.el (mh-loaddefs): Load rather than require.

> The removal of the provide statement from autoload-rubric was
> undocumented (it's a separate issue from generated-autoload-feature).

> If it was unintentional, I would prefer to put this back to how it was.

I hesitated, but in the end, given the fact that we now use files whose
non-directory names may clash, I think that auto-generating feature
names from files is too risky and not worth the trouble (and
generated-autoload-feature is not a solution since it is not at the
right place, and actually there's no right place for it).


        Stefan




  reply	other threads:[~2009-11-04  3:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1N5Tis-0002pY-NM@cvs.savannah.gnu.org>
2009-11-04  3:12 ` loaddefs and provide Glenn Morris
2009-11-04  3:58   ` Stefan Monnier [this message]
2009-11-04  8:37     ` Glenn Morris
2009-11-04  8:46       ` Glenn Morris
2009-11-04 18:36         ` Stefan Monnier
2009-11-04 19:11           ` Glenn Morris
2009-11-04 20:46             ` Stefan Monnier
2009-11-04 17:10     ` Chong Yidong
2009-11-04 20:45       ` Stefan Monnier
2009-11-10  2:11         ` Glenn Morris
2009-11-10 17:48           ` Stefan Monnier
2009-11-10 18:40             ` Chong Yidong
2009-11-04  9:54   ` Juanma Barranquero

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=jwvmy337xpo.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=rgm@gnu.org \
    /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 public inbox

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

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