Confirmation for auto-archive

[Uday Reddy]

Robert Marshall (viewmail-info, 2011--4-28):

One key binding which I would like to be more inaccessible is
vm-auto-archive-messages maybe it is not so much a trap for a new user
but I have lots of things in vm-auto-folder-alist and I only want to run
auto-archive infrequently and *never* on anything other than the INBOX.

Once you accidentally hit A there's no way back.....well apart from the
hard drive backup

[Uday Reddy (reddyuday)]

I do see that typing 'A' involves using at least two fingers (unless CAPS LOCK is turned on :-), which is a bit less accident-prone than just typing 'e'.

I can however add a confirmation dialogue to be gone through before the auto-archive kicks in. (I guess I would also need a variable to override the confirmation dialogue!)

[John Hein (xpqheqdvq4)]

I often do 'V S' or some other virtual folder and use 'A' to archive those messages. I'm wondering if the confirmation prompt might be annoying for people that do that. I can see the merit for a big INBOX with a random collection of read & unread messages, however. I guess I like the prompt, and hitting 'y' after 'A' isn't very burdensome. But I could see someone asking in the future for a way to disable that or set some sort of threshold (message count?).

[Uday Reddy (reddyuday)]

Added a variable `vm-confirm-for-auto-archive'. Revision 1313.

[John Hein (xpqheqdvq4)]

Before rev 1477, marking a number of messages and using 'M N A' to archive them would not prompt for confirmation. In rev 1477, auto-archive confirmation was again retooled a bit and now 'M N A' asks for confirmation. Before reopening this bug or a new one, I was just curious if that was by design. I think I liked it before (explicitly trying to archive marked messages wouldn't prompt for confirmation). Maybe making vm-confirm-for-auto-archive take on an extra level other than just t/nil to not prompt in certains cases (like 'M N A'). Thoughts?

[Uday Reddy (reddyuday)]

Thanks, John. The changes in 1477 were a bit buggy. Should be fixed in
rev. 1481.

[John Hein (xpqheqdvq4)]

Comment #4 fixed in 1482. Thanks.