unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "D. Goel" <deego@glue.umd.edu>
Cc: emacs-devel@gnu.org
Subject: Re: defvar vs setqif..
Date: 20 May 2002 15:08:00 -0400	[thread overview]
Message-ID: <ap3r8k6d4dr.fsf@poynting.umd.edu> (raw)
In-Reply-To: <1021841986.24318.2803.camel@space-ghost>


> On Sun, 2002-05-19 at 16:44, D. Goel wrote:
> 
> > An example: my .emacs needs to, say, (add-hook 'foo-mode-hook... ),
> > but the hook may not be defined, so i (defvar foo-mode-hook) before
> > this statement. 
> 
> Why do you defvar it?  The best solution is to (require 'foo-mode)
> before adding the hook. 

true i guess, but not always carried out... that's why the issue
arises in the first place..   One reason it is not always carried out
is:

say a user wants to frob a thousand variables in their .emacs or their
own private library...  they don't want to (require) all the involved
libraries, thus slowing down the loading of emacs.. so the user simply
make sures the variables are defined via defvar, and then runs
(add-to-list) or whatever on these variables..

authors who may do similar stuff in their libraries may have the same
reason---not wanting to slow down the loading by (requiring 'stuff).
So they may defvar variables of that libaray...



> But `add-hook' won't lose if the hook isn't bound yet.


yeah very true.. bad example, sorry :).. how about (add-to-list) ?  :)




D				   <http://www.glue.umd.edu/~deego/>
-- 

  parent reply	other threads:[~2002-05-20 19:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-19 20:44 defvar vs setqif D. Goel
2002-05-19 20:59 ` Colin Walters
2002-05-20  0:05   ` Miles Bader
2002-05-20 19:08   ` D. Goel [this message]
2002-05-20 19:41     ` Thien-Thi Nguyen
2002-05-20 19:47       ` Stefan Monnier
2002-05-21 13:13         ` D. Goel
2002-05-20 20:05     ` Kai Großjohann
2002-05-20 21:33   ` Richard Stallman
2002-05-20  0:03 ` Miles Bader
2002-05-20 19:00   ` D. Goel
2002-05-20 19:24     ` Stefan Monnier
2002-05-20 19:40       ` D. Goel
2002-05-20 23:15     ` Miles Bader
2002-05-21 13:18       ` D. Goel

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=ap3r8k6d4dr.fsf@poynting.umd.edu \
    --to=deego@glue.umd.edu \
    --cc=emacs-devel@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).