From: Lars Ingebrigtsen <larsi@gnus.org>
To: Brent Busby <brent@jfi.uchicago.edu>
Cc: 21105@debbugs.gnu.org
Subject: bug#21105: batch article move/copy to groups pompts user too much
Date: Thu, 26 Jan 2017 20:49:37 +0100 [thread overview]
Message-ID: <87wpdhmwj2.fsf@gnus.org> (raw)
In-Reply-To: <8xx8ua9jqj1.fsf@isildur.uchicago.edu> (Brent Busby's message of "Tue, 21 Jul 2015 13:48:18 -0500")
Sorry for the late response; due to a misunderstanding the Gnus bug
reports went to a part of the bug tracker I wasn't checking.
Brent Busby <brent@jfi.uchicago.edu> writes:
> However, if you're copying/moving articles to actual _groups_ (rather
> than raw files), gnus-prompt-before-saving has no effect. You can use
> gnus-move-split-methods to teach Gnus how to suggest moved/copied
> articles should be moved (described in section 3.26), but you can't use
> gnus-prompt-before-saving to avoid excessive prompting while doing so,
> nor is there any other variable analogous to gnus-prompt-before-saving
> that can affect article move/copy to groups.
I'm not sure I understand. If you `#' a bunch of articles, and then
move them with `B m', you should only be prompted once as to where to
move the articles. Are you prompted for every article instead?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next parent reply other threads:[~2017-01-26 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8xx8ua9jqj1.fsf@isildur.uchicago.edu>
2017-01-26 19:49 ` Lars Ingebrigtsen [this message]
2017-01-26 20:38 ` bug#21105: batch article move/copy to groups pompts user too much Brent Busby
2017-01-27 12:10 ` Lars Ingebrigtsen
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=87wpdhmwj2.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=21105@debbugs.gnu.org \
--cc=brent@jfi.uchicago.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.