From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Drew Adams <drew.adams@oracle.com>
Cc: 19232@debbugs.gnu.org
Subject: bug#19232: 25.0.50; ring.el: why not autoload `ring-member' etc.?
Date: Sun, 30 Nov 2014 22:59:39 -0500 [thread overview]
Message-ID: <jwv7fycyqar.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <0c8bdd78-ef47-4ce6-ae96-353a1920c5c1@default> (Drew Adams's message of "Sun, 30 Nov 2014 11:18:30 -0800 (PST)")
tags 19232 notabug
thanks
> Subject line says it all. Why make users `require' ring.el for such
> functions, or autoload them themselves? Do what you do now for `ringp'
> and `make-ring' for other functions as well, such as `ring-insert',
> `ring-member', and `ring-next'. This is a utility library.
I think the error is to autoload ring-p and make-ring. Of course it's
a bit late to fix it, but that's no reason to add many more autoloads.
Just (require 'ring) like everyone else if you use functions from that
library.
Stefan
prev parent reply other threads:[~2014-12-01 3:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 19:18 bug#19232: 25.0.50; ring.el: why not autoload `ring-member' etc.? Drew Adams
2014-12-01 3:59 ` Stefan Monnier [this message]
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=jwv7fycyqar.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=19232@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).