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: read messages becoming unread in nnml
Date: Wed, 13 Aug 2014 22:02:55 +0200	[thread overview]
Message-ID: <878umstaxc.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.7035.1407874665.1147.info-gnus-english@gnu.org>

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

>>> I.e. run the command that actually tells Gnus to
>>> close down, instead of explicitly calling a
>>> function to save the one file you happen know
>>> should be handled when shutting down (what if Gnus
>>> needs to do more now/in the future?)
>
>> I'm not worried about that.
>
> Ok, I give up.

No, I actually changed that. However, then you have to
do another thing, namely:

(setq gnus-expert-user t)

otherwise it'll prompt you if you really want to "quit
reading news" :) Of course, you never want to do that,
but sometimes you need to quit Emacs and shut down your
system just the same.

Thing is, I had

(setq gnus-novice-user nil)

already, as well as

(setq gnus-verbose 1)
(setq gnus-verbose-backends 1)

though those only set Gnus (not) talking, without
touching what to ask of the user.

So I didn't know not only you could opt-out being a
beginner, you can explicitly be an expert as well.

More specifically you can get away with the
confirmation on exit with `gnus-interactive-exit'.

-- 
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:[~2014-08-13 20:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.6902.1407653531.1147.info-gnus-english@gnu.org>
2014-08-10 20:52 ` Emanuel Berg
2014-08-11  9:17   ` Adam Sjøgren
2014-08-11 10:54     ` Julien Cubizolles
2014-08-11 10:51   ` Julien Cubizolles
2014-09-17  9:15     ` Julien Cubizolles
     [not found]   ` <mailman.6960.1407748672.1147.info-gnus-english@gnu.org>
2014-08-11 21:55     ` Emanuel Berg
2014-08-11 22:48       ` Adam Sjøgren
     [not found]       ` <mailman.6989.1407797356.1147.info-gnus-english@gnu.org>
2014-08-11 23:16         ` Emanuel Berg
2014-08-12 10:33           ` Adam Sjøgren
     [not found]           ` <mailman.7007.1407839648.1147.info-gnus-english@gnu.org>
2014-08-12 17:15             ` Emanuel Berg
2014-08-12 17:32               ` Adam Sjøgren
2014-08-12 17:32               ` Adam Sjøgren
     [not found]               ` <mailman.7028.1407864763.1147.info-gnus-english@gnu.org>
2014-08-12 17:59                 ` Emanuel Berg
2014-08-12 20:17                   ` Adam Sjøgren
     [not found]                   ` <mailman.7035.1407874665.1147.info-gnus-english@gnu.org>
2014-08-13 20:02                     ` Emanuel Berg [this message]
     [not found]               ` <mailman.7029.1407864916.1147.info-gnus-english@gnu.org>
2014-08-12 18:07                 ` Emanuel Berg
2014-08-12 17:21         ` Carlos Pita
2014-08-12 17:20           ` Emanuel Berg
2014-08-10  6:51 Julien Cubizolles

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=878umstaxc.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).