Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Alberto Luaces <aluaces@udc.es>
To: info-gnus-english@gnu.org
Subject: Re: When does gnus read .gnus.el variables
Date: Sat, 07 Mar 2015 20:22:22 +0100	[thread overview]
Message-ID: <87bnk4hat0.fsf@eps142.cdf.udc.es> (raw)
In-Reply-To: <87sidit1uf.fsf@topper.koldfront.dk>

asjo@koldfront.dk (Adam Sjøgren) writes:

> Alberto Luaces writes:
>

[...]

>> When I quit gnus *without quitting* emacs, and then restart gnus again,
>> nnimap-split-fancy stays with its initial value.
>
> Sound odd.
>
> What does C-h v nnimap-split-fancy say?
>
> Can you reproduce the problem??
>

Yes. C-h v nnimap-split-fancy says:

--8<---------------cut here---------------start------------->8---
nnimap-split-fancy's value is (|
 ("list-id" ...))
--8<---------------cut here---------------end--------------->8---

that is, the values specified in ~/.gnus.el when emacs was started.

Later, I modified the file to have an updated nnimap-split-fancy
definition.  I place the point after nnimap-split-fancy and press C-x
C-e, so now C-h v shows the new value and everything works as expected.

When I quit gnus pressing q, and then restart it with M-x gnus, the
variable is restored to its original value, not the one in ~/.gnus.el,
which is the one I have just manually set.

Maybe there is something special about this variable since its help info
says it is a "server variable".

-- 
Alberto


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2015-03-07 19:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 17:52 Alberto Luaces
2015-03-06 18:31 ` Adam Sjøgren
2015-03-07 19:22   ` Alberto Luaces [this message]
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=87bnk4hat0.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).