From: npostavs@users.sourceforge.net
To: Drew Adams <drew.adams@oracle.com>
Cc: 24845@debbugs.gnu.org
Subject: bug#24845: 24.5; out-of-date text in (elisp) `Autoload'?
Date: Tue, 01 Nov 2016 21:13:48 -0400 [thread overview]
Message-ID: <87oa1ypttf.fsf@users.sourceforge.net> (raw)
In-Reply-To: <73b474f6-2494-4b85-b92f-cee2830acd8a@default> (Drew Adams's message of "Tue, 1 Nov 2016 08:09:52 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> I see this in that node:
>
> Other definition types:
> defcustom, defgroup, defclass (*note EIEIO: (eieio)Top.), and
> define-skeleton (see the commentary in skeleton.el).
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> But I do not see anything appropriate in the commentary in
> `skeleton.el'. What is this all about?
The reference to skeleton.el's commentary was introduced in bc44be50 "*
loading.texi (Autoload): Explicitly state which forms are processed
specially.", there is no additional commentary in skeleton.el regarding
autoloading in that revision either. I think it's just intended to be
an explanation of what `define-skeleton' is.
Perhaps a better link would be `(autotype) Skeleton Language', similar
to how defclass has a link to eieio.
diff --git i/doc/lispref/loading.texi w/doc/lispref/loading.texi
index 81a1922..82bdde0 100644
--- i/doc/lispref/loading.texi
+++ w/doc/lispref/loading.texi
@@ -610,8 +610,8 @@ Autoload
@item Other definition types:
@code{defcustom}, @code{defgroup}, @code{defclass}
-(@pxref{Top,EIEIO,,eieio,EIEIO}), and @code{define-skeleton} (see the
-commentary in @file{skeleton.el}).
+(@pxref{Top,EIEIO,,eieio,EIEIO}), and @code{define-skeleton}
+(@pxref{Skeleton Language,,,autotype,Autotyping}).
@end table
You can also use a magic comment to execute a form at build time
next prev parent reply other threads:[~2016-11-02 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 15:09 bug#24845: 24.5; out-of-date text in (elisp) `Autoload'? Drew Adams
2016-11-02 1:13 ` npostavs [this message]
2016-11-02 15:51 ` Eli Zaretskii
2016-11-05 14:13 ` npostavs
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=87oa1ypttf.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=24845@debbugs.gnu.org \
--cc=drew.adams@oracle.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.
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).