From: Henrik Enberg <henrik.enberg@home.se>
Subject: Re: When is setq-default a bad idea? (It seems to simplify things over plain old setq.)
Date: Mon, 12 Jan 2004 20:34:40 +0100 [thread overview]
Message-ID: <87llodgdv3.fsf@home.se> (raw)
In-Reply-To: bf23f78f.0401121127.6f92fc40@posting.google.com
seberino@spawar.navy.mil (Christian Seberino) writes:
> If I use setq then I have to worry about minor modes and major modes
> overwriting my settings.
Only local variables are possibly overridden by modes. See the node
"Locals" in the Emacs manual for a comprehensive explanation of local
variables.
> It seems like setq-default is more comprehensive and overrides any
> attempted changes to variables elsewhere.
Not really. setq-default simply sets a default value of a variable, it
doesn't prevent changing that value later.
> When is it a problem if I use setq-default exclusively?
It's rather pointless with non-local variables, and uses more memory.
prev parent reply other threads:[~2004-01-12 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 19:27 When is setq-default a bad idea? (It seems to simplify things over plain old setq.) Christian Seberino
2004-01-12 19:34 ` Henrik Enberg [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=87llodgdv3.fsf@home.se \
--to=henrik.enberg@home.se \
/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).