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: Sun, 08 Mar 2015 01:31:20 +0100	[thread overview]
Message-ID: <87egp0xrc7.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.1615.1425765381.31049.info-gnus-english@gnu.org>

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

>>> So what did "Then that's it." mean?
>>
>> That's why .gnus.el isn't read when he first quits
>> Gnus and then restarts it, because none of that
>> actually happens.
>
> Why does that matter?

The key 'q' in *Group* should be `gnus-group-exit'
which should kill the *Group* buffer after which
(gnus-alive-p) should be nil, as in intuitive.

If the OP can explain why this doesn't happen it might
be disregarded but otherwise his system is br0ken and
fixing it may well fix this issue as well.

It is a partial explanation to his problem part of
which was "why does restarting Emacs set the variable,
but not restarting Gnus?" (pseudo-quote).

We have also encircled the problem as we know when the
variable is reset to its incorrect value.

The next step is: why isn't 'q' quitting Gnus, and
what in 'q' resets the variable? Go to *Group*,
`describe-key', `describe-function', then read the
code...

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

  parent reply	other threads:[~2015-03-08  0:31 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 [this message]
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=87egp0xrc7.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).