unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: 57144@debbugs.gnu.org
Subject: bug#57144: 29.0.50; Missing description for excluded files in docstring of loaddefs-generate
Date: Thu, 11 Aug 2022 21:31:32 +0200	[thread overview]
Message-ID: <86k07emvaj.fsf@gnu.org> (raw)

Hi all,

This is the docstring of `loaddefs-generate':

,----[ C-h f loaddefs-generate RET ]
| loaddefs-generate is an autoloaded Lisp function in ‘loaddefs-gen.el’.
| 
| (loaddefs-generate DIR OUTPUT-FILE &optional EXCLUDED-FILES EXTRA-DATA
| INCLUDE-PACKAGE-VERSION GENERATE-FULL)
| 
| Generate loaddefs files for Lisp files in the directories DIRS.
| DIR can be either a single directory or a list of directories.
| 
| The autoloads will be written to OUTPUT-FILE.  If any Lisp file
| binds ‘generated-autoload-file’ as a file-local variable, write
| its autoloads into the specified file instead.
| 
| The function does NOT recursively descend into subdirectories of the
| directory or directories specified.
| 
| If EXTRA-DATA, include this string at the start of the generated
| file.  This will also force generation of OUTPUT-FILE even if
| there are no autoloads to put into the file.
| 
| If INCLUDE-PACKAGE-VERSION, include package version data.
| 
| If GENERATE-FULL, don’t update, but regenerate all the loaddefs files.
`----

A description for EXCLUDED-FILES is missing.  It will a list containing
file names, but details should be added.

Best, Arash





             reply	other threads:[~2022-08-11 19:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 19:31 Arash Esbati [this message]
2022-08-12  6:50 ` bug#57144: 29.0.50; Missing description for excluded files in docstring of loaddefs-generate Eli Zaretskii
2022-08-12 17:51   ` Arash Esbati
2022-08-13 12:08     ` Lars Ingebrigtsen
2022-08-13 16:47       ` Arash Esbati
2022-08-15  6:33         ` Lars Ingebrigtsen
2022-08-15  9:48           ` Arash Esbati
2022-08-15 10:08             ` Lars 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

  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=86k07emvaj.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=57144@debbugs.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).