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: emacs-devel@gnu.org
Subject: Re: loaddefs and provide
Date: Wed, 04 Nov 2009 15:46:46 -0500	[thread overview]
Message-ID: <jwv3a4u588v.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <9liqdqm7g2.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 04 Nov 2009 14:11:09 -0500")

>>>> Perhaps there could be an optional argument
>>> (to autoload-rubric, I meant)
>> From where would it be provided?

> In custom-make-dependencies and finder-compile-keywords, if I
> understand the question correctly.

That would be fine, yes.

> -information contained in FILE."
> +information contained in FILE.  If FEATURE is non-nil, FILE
> +will provide a feature based on FILE."
>    (let ((basename (file-name-nondirectory file)))
>      (concat ";;; " basename
>  	    " --- automatically extracted " (or type "autoloads") "\n"
>  	    ";;\n"
>  	    ";;; Code:\n\n"
>  	    "\f\n"
> +	    (if feature
> +		(concat "(provide '" (file-name-sans-extension basename) ")\n")
> +	      "")

Better make FEATURE be the symbol to provide, rather than auto-compute
it based on the file name.  That's more flexible.


        Stefan




  reply	other threads:[~2009-11-04 20:46 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
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 [this message]
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=jwv3a4u588v.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --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).