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: Fri, 27 Jan 2017 13:10:37 +0100 [thread overview]
Message-ID: <871svovh36.fsf@mouse> (raw)
In-Reply-To: <8xx8tpxtv34.fsf@village.keycorner.org> (Brent Busby's message of "Thu, 26 Jan 2017 14:38:55 -0600")
Brent Busby <brent@jfi.uchicago.edu> writes:
> The only complaint I can think of now with Gnus' move/copy behavior is
> that usually it seems like there will be a partial string already typed
> for me *after* the prompt when I want to save or move something, and it
> will often not be the default choice that gnus-move-split-methods is
> trying to give me.
>
> Example: When I type 'B c' to copy this article to a different mail
> group, I get:
>
> Copy this article to (default nnfolder:uchicago): nnimap+jfimail.uchicago.edu:
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> The highlighted part is *after* the prompt, but I didn't type it.
I think it defaults to the last-entered group prefix, or the current
group prefix...
> It's
> also not the same as the default being suggested my
> gnus-move-split-methods in my configuration, which is being suggested in
> parenthesis in the prompt. It's offering me a default, and then typing
> for me something completely different that I can now hit enter on
> (defeating my default!).
If you just remove it, the default will be used.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2017-01-27 12:10 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 ` bug#21105: batch article move/copy to groups pompts user too much Lars Ingebrigtsen
2017-01-26 20:38 ` Brent Busby
2017-01-27 12:10 ` Lars Ingebrigtsen [this message]
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=871svovh36.fsf@mouse \
--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.