unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 34289@debbugs.gnu.org
Subject: bug#34289: Mention why killed groups come back anyway next time one starts gnus
Date: Sat, 22 Jun 2019 15:08:19 +0200	[thread overview]
Message-ID: <m35zoxdayk.fsf@gnus.org> (raw)
In-Reply-To: <87lg30xrvt.fsf@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Fri, 01 Feb 2019 08:40:54 +0800")

積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:

> On (info "(gnus) Subscription Commands")
> mention why killed groups come back anyway next time one starts gnus.
> See also http://jidanni.org/comp/configuration/
> Yes, it probably has to do with levels...
> OK mention that one must remove them from Mail/active too... and maybe by hand from .newsrc.eld .

No, you shouldn't have to do any of those things.  Killing a group with
C-k should leave them dead (on all the mainstream Gnus backends).

What groups display this behaviour?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2019-06-22 13:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01  0:40 bug#34289: Mention why killed groups come back anyway next time one starts gnus 積丹尼 Dan Jacobson
2019-02-02 16:47 ` Eric Abrahamsen
2019-06-22 13:08 ` Lars Ingebrigtsen [this message]
2019-06-23  1:10   ` 積丹尼 Dan Jacobson
2019-06-23 12:30     ` Lars Ingebrigtsen
2019-07-09 15:05       ` 積丹尼 Dan Jacobson
2019-07-09 15:18         ` Lars Ingebrigtsen
2019-07-09 15:35           ` 積丹尼 Dan Jacobson
2019-07-09 15:42             ` Lars Ingebrigtsen
2019-07-11  0:17               ` 積丹尼 Dan Jacobson
2019-07-11 14:08                 ` Lars Ingebrigtsen
2019-07-11 19:08                   ` 積丹尼 Dan Jacobson
2019-07-11 20:34                     ` Eric Abrahamsen
2019-07-13 22:53                       ` 積丹尼 Dan Jacobson

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m35zoxdayk.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=34289@debbugs.gnu.org \
    --cc=jidanni@jidanni.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).