From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master f995fbd: * lisp/server.el (server-name): Add autoload cookie. (Bug#23576)
Date: Thu, 19 May 2016 20:13:47 +0300 [thread overview]
Message-ID: <834m9u9dis.fsf@gnu.org> (raw)
In-Reply-To: <lglh36atfi.fsf@fencepost.gnu.org> (message from Glenn Morris on Thu, 19 May 2016 12:44:49 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Thu, 19 May 2016 12:44:49 -0400
>
> Eli Zaretskii wrote:
>
> > * lisp/server.el (server-name): Add autoload cookie. (Bug#23576)
> [...]
> > +;;;###autoload
> > (defcustom server-name "server"
>
> Autoloading defcustoms just so people can set them interactively before
> the associated package is loaded is a Bad Thing.
I don't understand why. Can you explain? That's not the only
defcustom that is marked as autoloaded.
> IMO it would have been better to simply remove the bit about
> set-variable from the manual.
I don't see why we should remove useful advice from the manual, just
because it's inconvenient to make it work.
next prev parent reply other threads:[~2016-05-19 17:13 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160518194708.27363.47377@vcs.savannah.gnu.org>
[not found] ` <20160518194708.86FE0220157@vcs.savannah.gnu.org>
2016-05-19 16:44 ` master f995fbd: * lisp/server.el (server-name): Add autoload cookie. (Bug#23576) Glenn Morris
2016-05-19 17:13 ` Eli Zaretskii [this message]
2016-05-20 4:07 ` Leo Liu
2016-05-20 5:51 ` Eli Zaretskii
2016-05-20 7:11 ` Leo Liu
2016-05-20 7:46 ` Eli Zaretskii
2016-05-20 8:48 ` Dmitry Gutov
2016-05-20 9:41 ` Eli Zaretskii
2016-05-20 12:12 ` Stefan Monnier
2016-05-20 13:34 ` Eli Zaretskii
2016-05-20 18:29 ` Stefan Monnier
2016-05-20 18:59 ` Eli Zaretskii
2016-05-26 3:01 ` Stefan Monnier
2016-05-26 3:36 ` Stefan Monnier
2016-05-26 15:38 ` Eli Zaretskii
2016-05-27 19:51 ` Stefan Monnier
2016-05-28 7:11 ` Eli Zaretskii
2016-06-17 16:42 ` Stefan Monnier
2016-06-17 20:35 ` Clément Pit--Claudel
2016-06-17 22:35 ` Stefan Monnier
2016-06-18 2:20 ` Clément Pit--Claudel
2016-06-18 2:38 ` Dmitry Gutov
2016-06-18 18:09 ` Stefan Monnier
2016-06-18 20:05 ` Dmitry Gutov
2016-06-23 13:45 ` Clément Pit--Claudel
2016-06-23 13:48 ` Clément Pit--Claudel
2016-06-23 14:27 ` Dmitry Gutov
2016-06-23 14:48 ` Clément Pit--Claudel
2016-06-23 14:30 ` Dmitry Gutov
2016-06-23 15:35 ` Stefan Monnier
2016-06-23 15:52 ` Dmitry Gutov
2016-06-24 14:01 ` Stefan Monnier
2016-07-01 13:33 ` Robert Weiner
2016-07-01 15:51 ` Stefan Monnier
2016-05-20 17:30 ` Glenn Morris
2016-05-20 17:47 ` Eli Zaretskii
2016-05-20 18:15 ` Dmitry Gutov
2016-05-20 18:55 ` Eli Zaretskii
2016-05-21 4:25 ` Leo Liu
2016-05-21 6:52 ` Eli Zaretskii
2016-05-21 7:05 ` Dmitry Gutov
2016-05-21 7:32 ` Eli Zaretskii
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=834m9u9dis.fsf@gnu.org \
--to=eliz@gnu.org \
--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).