From: Christian Lynbech <christian@defun.dk>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: ding@gnus.org
Subject: Re: Can't process mark all articles in summary
Date: Fri, 05 Jul 2019 09:04:48 +0200 [thread overview]
Message-ID: <m2muht0xnz.fsf@defun.dk> (raw)
In-Reply-To: <87a7duoijt.fsf@bobnewell.net> (Bob Newell's message of "Wed, 03 Jul 2019 12:32:54 -1000")
Strange, it works for me (eg. using M P R .) even with threaded summary.
Can you have added some configfuration/package that interacts with the
function?
--
------------------------+-----------------------------------------------------
Christian Lynbech | christian #\@ defun #\. dk
------------------------+-----------------------------------------------------
Hit the philistines three times over the head with the Elisp reference manual.
- petonic@hal.com (Michael A. Petonic)
-----------------------
On Wed, Jul 03 2019, Bob Newell wrote:
Brief follow-up.
> The following problem occurs: I want to process mark all articles in the
> (say) Trash summary buffer (though the issue is not limited to any one
> summary). So I try (gnus-uu-mark-buffer) or other
> desperate things like (gnus-summary-mark-as-processable 10000) from the
> top of the buffer.
I found that I can mark all articles if I turn off threading and
regenerate the summary buffer in unthreaded mode.
But who runs in unthreaded mode? And why shouldn't we be able to mark
all articles in threaded mode? I have yet to figure out /why/ this is
the case ... it's getting a bit on the deep side for me!
> Of course I can mark them one by one with a little bit of elisp, but it
> seems the 'mark all' commands should, well, mark all.
Alas, not so, again, unless I turn off threading.
--
Bob Newell
Honolulu, Hawai`i
* Via Gnus/BBDB/Org/Emacs/Linux *
next prev parent reply other threads:[~2019-07-05 7:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 21:02 Bob Newell
2019-07-03 22:32 ` Bob Newell
2019-07-05 7:04 ` Christian Lynbech [this message]
2019-07-05 18:57 ` Bob Newell
2019-07-04 13:15 ` Lars Ingebrigtsen
2019-07-04 19:26 ` Bob Newell
2019-07-04 22:31 ` Bob Newell
2019-07-06 2:33 ` Bob Newell
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=m2muht0xnz.fsf@defun.dk \
--to=christian@defun.dk \
--cc=bobnewell@bobnewell.net \
--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).