From: lee <lee@yagibdah.de>
To: ding@gnus.org
Subject: Re: storing messages into an mbox file
Date: Sun, 17 May 2015 11:02:50 +0200 [thread overview]
Message-ID: <87a8x3mv9h.fsf@heimdali.yagibdah.de> (raw)
In-Reply-To: <87iobw5ap1.fsf@uwo.ca> (Dan Christensen's message of "Wed, 13 May 2015 19:17:46 -0400")
Dan Christensen <jdc@uwo.ca> writes:
> lee <lee@yagibdah.de> writes:
>
>> Now I can't even find out where the mails are stored, how to delete
>> obsolete groups and how to make sure that the data gnus uses is clean.
>> These are very simple and basic questions, with no answers to them.
>
> As far as I've seen, your questions have been answered:
>
> `C-u G DEL' deletes editable groups, and `C-k' deletes others
> (such as nndoc and nndir groups, which are groups where Gnus
> never changes the content).
C-k doesn't delete groups, it only hides them, and speaking of "killing"
a group is misleading here. It does not delete the files the messages
are in. C-u G DEL seems to leave files behind as well, like the
directories the messages of the group were in.
This is untidy and a bug. When I delete a group, it needs to be
deleted, including the files and directories and whatever data gnus
stores about it.
> The Incoming files you thought were remnants of a group are just
> temporary files stored by development versions of Gnus.
Who knows, perhaps it will keep these files because they have been
assigned to an mbox.
> If those don't completely answer your questions, you'll have to
> give specific information:
>
> What groups can't you delete? What backend do they use?
I don't know any groups that could actually be deleted, no matter what
backend they use.
> Where are the files that you think aren't being deleted?
They are in ~/Mail.
--
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us. Finally, this fear has become reasonable.
next prev parent reply other threads:[~2015-05-17 9:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 19:03 lee
2015-04-28 20:03 ` Andreas Schwab
2015-04-29 19:32 ` lee
2015-04-29 20:10 ` Andreas Schwab
2015-04-29 20:37 ` this group and gnu.emacs.gnus (was: Re: storing messages into an mbox file) Emanuel Berg
2015-04-29 23:02 ` storing messages into an mbox file lee
2015-04-30 0:40 ` Eric Abrahamsen
2015-05-04 5:50 ` lee
2015-05-04 6:01 ` Adam Sjøgren
2015-05-07 23:11 ` lee
2015-05-08 9:22 ` Adam Sjøgren
2015-05-09 14:49 ` lee
2015-05-09 15:16 ` Adam Sjøgren
2015-05-10 12:39 ` Eric S Fraga
2015-05-12 8:06 ` Steinar Bang
2015-05-12 9:04 ` Eric S Fraga
2015-05-13 20:07 ` lee
2015-05-13 21:48 ` Adam Sjøgren
2015-05-17 8:46 ` lee
2015-05-13 23:17 ` Dan Christensen
2015-05-14 6:13 ` Steinar Bang
2015-05-17 9:02 ` lee [this message]
2015-05-14 6:10 ` Steinar Bang
2015-05-17 9:06 ` lee
2015-05-17 19:42 ` Steinar Bang
2015-05-17 20:45 ` Peter Münster
2015-05-14 9:19 ` e.fraga
2015-05-17 9:40 ` lee
2015-05-17 13:04 ` Eric S Fraga
2015-05-04 6:07 ` Eric Abrahamsen
2015-05-07 23:14 ` lee
2015-04-30 9:47 ` Andreas Schwab
2015-05-04 5:45 ` lee
2015-05-07 23:53 ` Dan Christensen
2015-05-08 22:10 ` lee
2015-05-18 2:25 ` Nikolaus Rath
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=87a8x3mv9h.fsf@heimdali.yagibdah.de \
--to=lee@yagibdah.de \
--cc=ding@gnus.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).