From: Alberto Luaces <aluaces@udc.es>
To: info-gnus-english@gnu.org
Subject: When does gnus read .gnus.el variables
Date: Thu, 05 Mar 2015 18:52:29 +0100 [thread overview]
Message-ID: <87zj7rjpr6.fsf@eps142.cdf.udc.es> (raw)
Hi,
this could be more of an elisp question rather than a gnus question, but
there it goes:
Once I have gnus up and running, I want to modify my nnimap-split-fancy
variable. Therefore, I evaluate a sexp with the new values, and change
.gnus.el accordingly for future sessions. All works ok.
When I quit gnus *without quitting* emacs, and then restart gnus again,
nnimap-split-fancy stays with its initial value. Maybe it is no
surprise that it is not reading .gnus.el again, but I wonder why my
on-the-fly settings were also dropped.
Any chance of setting this variable without having to restart emacs?
Thanks,
--
Alberto
next reply other threads:[~2015-03-05 17:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 17:52 Alberto Luaces [this message]
2015-03-06 18:31 ` Adam Sjøgren
2015-03-07 19:22 ` Alberto Luaces
2015-03-07 20:33 ` Adam Sjøgren
[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
2015-03-08 0:53 ` Emanuel Berg
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=87zj7rjpr6.fsf@eps142.cdf.udc.es \
--to=aluaces@udc.es \
--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).