all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net
Cc: 24845@debbugs.gnu.org
Subject: bug#24845: 24.5; out-of-date text in (elisp) `Autoload'?
Date: Wed, 02 Nov 2016 17:51:48 +0200	[thread overview]
Message-ID: <83k2clnaln.fsf@gnu.org> (raw)
In-Reply-To: <87oa1ypttf.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)

> From: npostavs@users.sourceforge.net
> Date: Tue, 01 Nov 2016 21:13:48 -0400
> Cc: 24845@debbugs.gnu.org
> 
> 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.

Indeed, that's also my impression.

> Perhaps a better link would be `(autotype) Skeleton Language', similar
> to how defclass has a link to eieio.

I think we should link to "Using Skeletons", or maybe even to "Top" in
that manual, since the cross-reference is meant for those readers who
don't know what skeletons are.

Thanks.





  reply	other threads:[~2016-11-02 15:51 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
2016-11-02 15:51   ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83k2clnaln.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24845@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.