From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: defcustom: changing from defvar - order of execution
Date: Fri, 6 May 2005 11:19:31 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICOELJCHAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87k6mcgsts.fsf-monnier+gnu.emacs.help@gnu.org>
> I see things like this fairly commonly, at the top level of
the standard
> Emacs libraries:
All these examples don't seem relevant since nowhere is it
suggested to the user to load the library in her .emacs.
Fair enough. But if a user does end up loading such a library during startup
(i.e. via .emacs) - whether by autoload or explicit load, the problem
arises, no?
> To me, it makes sense to generally avoid using user options
at the top level
> of the library that defines them, but I'm not sure such
avoidance is always
> feasible.
What makes more sense is to discourage loading of packages in .emacs.
Instead users should only set vars, setup autoloads, ...
Granted, but what if a user wants to systematically do something at startup
that is provided by a library? Autoload etc. are fine, but what if the user
wants to call a library-defined function at each startup? Whether it's a
command to show daily appointments or whatever...
Users do sometimes call functions at top level in their .emacs; those
functions are sometimes defined by libraries that are loaded by the .emacs
(whether via autoload, require, or load-library); and the called functions
sometimes depend on user options defined in those same libraries. Is this
just "bad practice" on the part of users?
next prev parent reply other threads:[~2005-05-06 18:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3763.1115399076.2819.help-gnu-emacs@gnu.org>
2005-05-06 17:38 ` defcustom: changing from defvar - order of execution Stefan Monnier
2005-05-06 18:19 ` Drew Adams [this message]
2005-05-10 16:14 ` Per Abrahamsen
2005-05-10 18:32 ` Drew Adams
2005-05-11 15:08 ` customization; std vs. personal libraries ken
[not found] ` <mailman.4670.1115825568.2819.help-gnu-emacs@gnu.org>
2005-05-11 23:12 ` Thien-Thi Nguyen
2005-05-19 15:22 ` Per Abrahamsen
2005-05-19 17:55 ` Kevin Rodgers
[not found] <mailman.4674.1115829901.2819.help-gnu-emacs@gnu.org>
2005-05-11 18:32 ` defcustom: changing from defvar - order of execution Stefan Monnier
[not found] <mailman.4474.1115750087.2819.help-gnu-emacs@gnu.org>
2005-05-11 14:07 ` Stefan Monnier
2005-05-11 16:36 ` Drew Adams
2005-05-11 16:37 ` Drew Adams
[not found] <mailman.3782.1115404280.2819.help-gnu-emacs@gnu.org>
2005-05-07 15:56 ` Stefan Monnier
[not found] <mailman.3356.1115247555.2819.help-gnu-emacs@gnu.org>
2005-05-06 3:20 ` Stefan Monnier
2005-05-06 17:00 ` Drew Adams
2005-05-03 15:50 Drew Adams
2005-05-03 16:13 ` Drew Adams
[not found] ` <mailman.3227.1115174847.2819.help-gnu-emacs@gnu.org>
2005-05-04 15:03 ` Stefan Monnier
2005-05-04 22:49 ` Drew Adams
2005-05-04 15:51 ` rgb
2005-05-04 22:49 ` Drew Adams
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=DNEMKBNJBGPAOPIJOOICOELJCHAA.drew.adams@oracle.com \
--to=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.
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).