Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: When does gnus read .gnus.el variables
Date: Fri, 06 Mar 2015 00:55:54 +0100	[thread overview]
Message-ID: <87zj7rf185.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.1406.1425577978.31049.info-gnus-english@gnu.org>

Alberto Luaces <aluaces@udc.es> writes:

> this could be more of an elisp question rather than
> a gnus question

Well, Gnus is Elisp so that should be OK.

> 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.

What do you have as `gnus-init-file'? Do you really
have ~/.gnus.el and not plain ~/.gnus?

It says in the help - 

    If a file with the `.el' or `.elc' suffixes
    exists, it will be read instead.

- so make sure there isn't any interference from other
files.

If you got that right, it gets worse. I don't have
"nnimap-split-fancy" so I can't confirm this, but in
principle you are not doing anything wrong. ~/.gnus
(or .el, or .elc) is read by Gnus on startup (i.e.,
Gnus and not Emacs startup) - you should be able to
verify this by putting for example

    (message "Gnus is starting")

in ~/.gnus (...) and then kill the *Group* buffer and
do (gnus). Then check the *Messages* if the message is
there.

If it doesn't show up it may be you have compiled the
file so Gnus uses that instead. In that case you
should recompile the file with the changes. Even so,
that should be the same situation when you restart
Emacs, so that shouldn't "help".

And: have you checked all other init files there is no
other mention of "nnimap-split-fancy"?

-- 
underground experts united

       reply	other threads:[~2015-03-05 23:55 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 [this message]
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
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=87zj7rf185.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).