From: David Z Maze <dmaze@MIT.EDU>
Subject: Re: deleting last article in nnmh?
Date: Tue, 04 Apr 2006 13:38:48 -0400 [thread overview]
Message-ID: <y68wte5i6l3.fsf@contents-vnder-pressvre.mit.edu> (raw)
In-Reply-To: <smuacb1ml28.fsf@linuxpal.mit.edu> (gdt@work.lexort.com's message of "Tue, 04 Apr 2006 11:12:31 -0400")
gdt@work.lexort.com writes:
> I have an nnmh select method and a lot of groups, and can do most
> operations fine.
>
> When I enter a group nnmh:foo, and then do
>
> M P a # set process mark on all articles
> B m nnimap+my.domain:lists.foo
>
> the last article is not moved. Trying to B m just that article
> fails, and G DEL also won't delete it. (I've done B c and the rm -rf
> of the directory.)
This is a "feature" of nnmh. In Gnus's newsreaderly view of the
world, article numbers need to be monotonically increasing, but in
nnmh the only state is the article numbers themselves. I can't find a
mention of it in the manual, though. nnmh.el defines a function
nnmh-deletable-article-p which is called from a couple of places with
a comment "We can never delete the last article in the group"; you
could conceivably set
;; Don't even think about setting this variable. It does not exist.
;; Forget about it. Uh-huh. Nope. Nobody here. It's only bound
;; dynamically by certain functions in nndraft.
(defvar nnmh-allow-delete-final nil)
to t.
Unless you're actively using another MH-based mail client (MH-E,
scan/show/...) you might consider using nnml as a mail backend instead
of nnmh. It has the same one-file-per-message format ("you can still
grep your mail") with an added .overview file that contains the
subjects and senders of each message, which makes scanning a folder a
lot faster.
--dzm
next prev parent reply other threads:[~2006-04-04 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 15:12 gdt
2006-04-04 17:38 ` David Z Maze [this message]
2006-04-04 23:30 ` gdt
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=y68wte5i6l3.fsf@contents-vnder-pressvre.mit.edu \
--to=dmaze@mit.edu \
/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).