From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: When does gnus read .gnus.el variables
Date: Sat, 07 Mar 2015 21:58:21 +0100 [thread overview]
Message-ID: <87zj7oy176.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.1601.1425756311.31049.info-gnus-english@gnu.org>
Alberto Luaces <aluaces@udc.es> writes:
>> Again, did you check out `gnus-init-file'? What
>> does it say? Evaluate any of these lines to find
>> out: gnus-init-file (describe-variable
>> 'gnus-init-file)
>
> It says "~/.gnus".
OK, which you don't have?
And you don't load .gnus.el explicitly, e.g., in
.emacs, for example with `load-library' or
`load-file'?
>> Also, what do you mean when you say you "quit
>> Gnus"?
>
> Pressing q on the Groups buffer, that is
> gnus-group-exit.
>
> (gnus-alive-p) returns t.
I have never heard of "Emacs server variables" and
there isn't anything in the documentation of `defvar'
that even remotely touches upon that (the confusing
part which shouldn't relate is the lexical vs. dynamic
scope which has basically to do with `let' clauses -
in lexical, if you do a `let', then value-key
replacement are only in effect in that particular
clause, and not in code invoked from it, where the
same key - if present - will be left alone). Anyway,
if the variable was defined with `defvar' it shouldn't
be a problem because that interface is simple:
(defvar SYMBOL &optional INITVALUE DOCSTRING)
... The optional argument INITVALUE is evaluated,
and used to set SYMBOL, only if SYMBOL's value is
void.
However, if the variable is defined with `defcustom' -
which makes it a so-called user variable - it says
(defcustom SYMBOL STANDARD DOC &rest ARGS)
STANDARD is an expression specifying the
variable's standard value. It should not be
quoted. It is evaluated once by `defcustom', and
the value is assigned to SYMBOL if the variable is
unbound. The expression itself is also stored, so
that Customize can re-evaluate it later to get the
standard value.
Do you do anything that would provoke Customize to
re-evaluate the standard value? (By the way, what
value does it have before and after you exit Gnus?)
--
underground experts united
next prev parent reply other threads:[~2015-03-07 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1406.1425577978.31049.info-gnus-english@gnu.org>
2015-03-05 23:55 ` Emanuel Berg
2015-03-06 17:57 ` Alberto Luaces
[not found] ` <mailman.1508.1425664677.31049.info-gnus-english@gnu.org>
2015-03-07 15:46 ` Emanuel Berg
2015-03-07 19:19 ` Alberto Luaces
2015-03-07 20:35 ` Adam Sjøgren
[not found] ` <mailman.1606.1425760812.31049.info-gnus-english@gnu.org>
2015-03-07 21:02 ` Emanuel Berg
2015-03-07 21:03 ` Adam Sjøgren
[not found] ` <mailman.1610.1425762253.31049.info-gnus-english@gnu.org>
2015-03-07 21:28 ` Emanuel Berg
2015-03-07 21:35 ` Adam Sjøgren
[not found] ` <mailman.1614.1425764141.31049.info-gnus-english@gnu.org>
2015-03-07 21:46 ` Emanuel Berg
2015-03-07 21:56 ` Adam Sjøgren
[not found] ` <mailman.1615.1425765381.31049.info-gnus-english@gnu.org>
2015-03-08 0:31 ` Emanuel Berg
2015-03-09 17:49 ` Alberto Luaces
[not found] ` <mailman.1601.1425756311.31049.info-gnus-english@gnu.org>
2015-03-07 20:58 ` Emanuel Berg [this message]
2015-03-08 0:53 ` Emanuel Berg
2015-03-05 17:52 Alberto Luaces
2015-03-06 18:31 ` Adam Sjøgren
2015-03-07 19:22 ` Alberto Luaces
2015-03-07 20:33 ` Adam Sjøgren
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zj7oy176.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=info-gnus-english@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.
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 NNTP newsgroup(s).