VM

auto-archive messages cluttered

Bug #633532 reported by Bar Shirtcliff
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VM
Fix Released
Low
Uday Reddy

Bug Description

When I use auto-archive to save a bunch of messages from my inbox to the places listed in my auto-archive-alist, I get an annoying mess in the minibuffer:

24 archived, still working...
Retrieving message body... done
1 message saved to /Users/bar/mail/python
25 archived, still working...
Retrieving message body... done
1 message saved to /Users/bar/mail/python
26 archived, still working...
Retrieving message body... done
1 message saved to /Users/bar/mail/python
27 archived, still working...

which just looks like a blur at the speed at which vm works.
What happened to the old way? It was like this:
27 archived, still working...
27 archived, still working...
27 archived, still working...
27 archived, still working...
27 archived, still working...
(pretend incrementation, there)
so that one would see the numbers change in the minibuffer... much more informative and less scary. =)

Related branches

Revision history for this message
Tim Cross (tcross) wrote :

Thanks for the report.

Can you indicate which version of VM and emacs you are using?

Also, if possible, can you attach the custom function you use for auto-archiving. This will allow us to test with the same/similar environment.

Revision history for this message
Bar Shirtcliff (barshirtcliff) wrote :

Sure thing. Sorry for not providing that in the first place.

VM version is: 8.1.92a
GNU Emacs 23.2.50.3 (x86_64-apple-darwin10.4.0, NS apple-appkit-1038.32) of 2010-08-19 on bar-macbook.local - Aquamacs Distribution 2.1

 vm-auto-folder-alist ... I'm not using any custom function for archiving, so far as I know. The only relevant variable I see, besides the alist, is

vm-auto-folder-case-fold-search t

Thanks.

Revision history for this message
Uday Reddy (reddyuday) wrote : Re: [Bug 633532] [NEW] auto-archive messages cluttered

On Wed, 08 Sep 2010 20:41:33 -0000, Bar Shirtcliff
<email address hidden> wrote:
> Public bug reported:
>
> When I use auto-archive to save a bunch of messages from my inbox to the
> places listed in my auto-archive-alist, I get an annoying mess in the
> minibuffer:
>
> 24 archived, still working...
> Retrieving message body... done
> 1 message saved to /Users/bar/mail/python

The "Retrieving message body..." message comes about when the message body
is being retrieved from an IMAP server. Are you using headers-only
operation here?

I will have to look more closely at the mini-buffer messages more closely
at some point.

Cheers,
Uday

Revision history for this message
Bar Shirtcliff (bar-cs) wrote :

Hi Uday,

I'm not using IMAP at all. I use fetchmail, and messages are fetched
all at once from a crash box.

What does that mean, headers-only operation? How can I check to see
whether I am using it or not? The messages are displayed in the INBOX
Presentation buffer.

There is one bit of custom code that happens when a message is chosen
in the Summary window. I'll try turning that off and see how that
does. I had forgotten all about it.

Best,
Bar

Uday Reddy writes:
| On Wed, 08 Sep 2010 20:41:33 -0000, Bar Shirtcliff
| <email address hidden> wrote:
| > Public bug reported:
| >
| > When I use auto-archive to save a bunch of messages from my inbox to the
| > places listed in my auto-archive-alist, I get an annoying mess in the
| > minibuffer:
| >
| > 24 archived, still working...
| > Retrieving message body... done
| > 1 message saved to /Users/bar/mail/python
|
| The "Retrieving message body..." message comes about when the message body
| is being retrieved from an IMAP server. Are you using headers-only
| operation here?
|
| I will have to look more closely at the mini-buffer messages more closely
| at some point.
|
| Cheers,
| Uday
|
| --
| auto-archive messages cluttered
| https://bugs.launchpad.net/bugs/633532
| You received this bug notification because you are subscribed to VM.
|
| Status in VM (View Mail) for Emacs: New
|
| Bug description:
| When I use auto-archive to save a bunch of messages from my inbox to the places listed in my auto-archive-alist, I get an annoying mess in the minibuffer:
|
| 24 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 25 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 26 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 27 archived, still working...
|
| which just looks like a blur at the speed at which vm works.
| What happened to the old way? It was like this:
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| (pretend incrementation, there)
| so that one would see the numbers change in the minibuffer... much more informative and less scary. =)

--

Revision history for this message
Tim Cross (tcross) wrote :
Download full text (4.7 KiB)

Just a qucik reply as Uday is travelling at the moment and may not be able to
reply very quickly.

The reference to headers-only is only relevant if you are using IMAP. It is
just an optimisation option to speed up things where only the headers are
downloaded rather than downloading the headers and body.

As your using fetchmail (same approach I use), it is not relevant.
Unfortunately, I don't use auto archiving, but will try to set something up and
see if I can reproduce what your seeing and then see what is generating the
messages. I may have some issues as I use emacspeak and from memory, it has
code to quieten down the messages from VM. If this is the case, things may need
to wait until Uday returns.

Tim

Bar Shirtcliff writes: > Hi Uday,
 >
 > I'm not using IMAP at all. I use fetchmail, and messages are fetched
 > all at once from a crash box.
 >
 > What does that mean, headers-only operation? How can I check to see
 > whether I am using it or not? The messages are displayed in the INBOX
 > Presentation buffer.
 >
 > There is one bit of custom code that happens when a message is chosen
 > in the Summary window. I'll try turning that off and see how that
 > does. I had forgotten all about it.
 >
 > Best,
 > Bar
 >
 >
 > Uday Reddy writes:
 > | On Wed, 08 Sep 2010 20:41:33 -0000, Bar Shirtcliff
 > | <email address hidden> wrote:
 > | > Public bug reported:
 > | >
 > | > When I use auto-archive to save a bunch of messages from my inbox to the
 > | > places listed in my auto-archive-alist, I get an annoying mess in the
 > | > minibuffer:
 > | >
 > | > 24 archived, still working...
 > | > Retrieving message body... done
 > | > 1 message saved to /Users/bar/mail/python
 > |
 > | The "Retrieving message body..." message comes about when the message body
 > | is being retrieved from an IMAP server. Are you using headers-only
 > | operation here?
 > |
 > | I will have to look more closely at the mini-buffer messages more closely
 > | at some point.
 > |
 > | Cheers,
 > | Uday
 > |
 > | --
 > | auto-archive messages cluttered
 > | https://bugs.launchpad.net/bugs/633532
 > | You received this bug notification because you are subscribed to VM.
 > |
 > | Status in VM (View Mail) for Emacs: New
 > |
 > | Bug description:
 > | When I use auto-archive to save a bunch of messages from my inbox to the
places listed in my auto-archive-alist, I get an annoying mess in the
minibuffer:
 > |
 > | 24 archived, still working...
 > | Retrieving message body... done
 > | 1 message saved to /Users/bar/mail/python
 > | 25 archived, still working...
 > | Retrieving message body... done
 > | 1 message saved to /Users/bar/mail/python
 > | 26 archived, still working...
 > | Retrieving message body... done
 > | 1 message saved to /Users/bar/mail/python
 > | 27 archived, still working...
 > |
 > | which just looks like a blur at the speed at which vm works.
 > | What happened to the old way? It was like this:
 > | 27 archived, still working...
 > | 27 archived, still working...
 > | 27 archived, still working...
 > | 27 archived, still working...
 > | 27 archived, still working...
 > | (pretend incrementation, there)
 > | so that one would...

Read more...

Revision history for this message
Uday Reddy (reddyuday) wrote :

On Thu, 09 Sep 2010 23:37:16 -0000, Bar Shirtcliff
<email address hidden> wrote:

> I'm not using IMAP at all. I use fetchmail, and messages are fetched
> all at once from a crash box.

In that case, the "Retrieving message body..." message is in error. This
is probably fixed in the latest release, but I can't be sure. I will take
a look after I return next week.

Changed in vm:
status: New → Triaged
importance: Undecided → Low
assignee: nobody → Uday Reddy (reddyuday)
milestone: none → 8.1.94a
tags: added: headers-only
Revision history for this message
Bar Shirtcliff (bar-cs) wrote : [Bug 633532] Re: auto-archive messages cluttered

Hi Uday,

I did bzr pull and recompiled. It's a much faster blur, now. =)

Best,
Bar

Uday Reddy writes:
| On Thu, 09 Sep 2010 23:37:16 -0000, Bar Shirtcliff
| <email address hidden> wrote:
|
| > I'm not using IMAP at all. I use fetchmail, and messages are fetched
| > all at once from a crash box.
|
| In that case, the "Retrieving message body..." message is in error. This
| is probably fixed in the latest release, but I can't be sure. I will take
| a look after I return next week.
|
|
| ** Changed in: vm
| Status: New => Triaged
|
| ** Changed in: vm
| Importance: Undecided => Low
|
| ** Changed in: vm
| Assignee: (unassigned) => Uday Reddy (reddyuday)
|
| ** Changed in: vm
| Milestone: None => 8.1.94a
|
| ** Tags added: headers-only
|
| --
| auto-archive messages cluttered
| https://bugs.launchpad.net/bugs/633532
| You received this bug notification because you are subscribed to VM.
|
| Status in VM (View Mail) for Emacs: Triaged
|
| Bug description:
| When I use auto-archive to save a bunch of messages from my inbox to the places listed in my auto-archive-alist, I get an annoying mess in the minibuffer:
|
| 24 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 25 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 26 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 27 archived, still working...
|
| which just looks like a blur at the speed at which vm works.
| What happened to the old way? It was like this:
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| (pretend incrementation, there)
| so that one would see the numbers change in the minibuffer... much more informative and less scary. =)

--

Uday Reddy (reddyuday)
Changed in vm:
status: Triaged → Fix Committed
Revision history for this message
Bar Shirtcliff (bar-cs) wrote :

Thanks!

Uday Reddy writes:
| ** Changed in: vm
| Status: Triaged => Fix Committed
|
| --
| auto-archive messages cluttered
| https://bugs.launchpad.net/bugs/633532
| You received this bug notification because you are subscribed to VM.
|
| Status in VM (View Mail) for Emacs: Fix Committed
|
| Bug description:
| When I use auto-archive to save a bunch of messages from my inbox to the places listed in my auto-archive-alist, I get an annoying mess in the minibuffer:
|
| 24 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 25 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 26 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 27 archived, still working...
|
| which just looks like a blur at the speed at which vm works.
| What happened to the old way? It was like this:
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| (pretend incrementation, there)
| so that one would see the numbers change in the minibuffer... much more informative and less scary. =)

--

Revision history for this message
Uday Reddy (reddyuday) wrote :

Bar Shirtcliff writes:

> Thanks!

You are welcome. Please let me know if it works correctly. I haven't
tested it fully because I don't have a good set-up for auto-archiv.

Cheers,
Uday

Revision history for this message
Bar Shirtcliff (bar-cs) wrote :

Hi Uday,

oopss... no, it isn't fixed. still the blur.

If you want a simple test setup, save one message to file, create an
auto-archive list that would file that message somewhere, make 20
copies of the new message file in one file, comment out however you
recieve the mail in your vm init file and restart emacs, then, in VM,
open the 'folder' and auto-archive the messages. You should see the
blur.

I'm assuming it's how you use VM that prevents you from using
auto-archive. That makes testing just a matter of temporarily
commenting out lines.

Bar

Uday Reddy writes:
| Bar Shirtcliff writes:
|
| > Thanks!
|
| You are welcome. Please let me know if it works correctly. I haven't
| tested it fully because I don't have a good set-up for auto-archiv.
|
| Cheers,
| Uday
|
| --
| auto-archive messages cluttered
| https://bugs.launchpad.net/bugs/633532
| You received this bug notification because you are a direct subscriber
| of the bug.
|
| Status in VM (View Mail) for Emacs: Fix Committed
|
| Bug description:
| When I use auto-archive to save a bunch of messages from my inbox to the places listed in my auto-archive-alist, I get an annoying mess in the minibuffer:
|
| 24 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 25 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 26 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 27 archived, still working...
|
| which just looks like a blur at the speed at which vm works.
| What happened to the old way? It was like this:
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| (pretend incrementation, there)
| so that one would see the numbers change in the minibuffer... much more informative and less scary. =)
|
| To unsubscribe from this bug, go to:
| https://bugs.launchpad.net/vm/+bug/633532/+subscribe

--

Revision history for this message
Uday Reddy (reddyuday) wrote :

Bar Shirtcliff writes:

> If you want a simple test setup, save one message to file, create an
> auto-archive list that would file that message somewhere, make 20
> copies of the new message file in one file, comment out however you
> recieve the mail in your vm init file and restart emacs, then, in VM,
> open the 'folder' and auto-archive the messages. You should see the
> blur.

Nice trick! I tried it and it is working fine for me. Make sure that
you are using revision 957 from the trunk. 'bzr log -l1' can tell you
the verison number.

> I'm assuming it's how you use VM that prevents you from using
> auto-archive. That makes testing just a matter of temporarily
> commenting out lines.

Actually, I use the auto-folder-alist to determine the folder for
manual saving. If I use it to auto-archive, huge amount of junk from
my INBOX will get saved in tons of folders, which will be hard to
clean up later on.

Cheers,
Uday

Revision history for this message
Bar Shirtcliff (barshirtcliff) wrote :

Aha!!

You're right. It's fixed. Thank you very much.
=)

I use procmail to filter out junk and redirect lists-mail, etc. I
highly recommend it, fwiw. No junk makes it to my Inbox.

Bar

Uday Reddy writes:
| Bar Shirtcliff writes:
|
| > If you want a simple test setup, save one message to file, create an
| > auto-archive list that would file that message somewhere, make 20
| > copies of the new message file in one file, comment out however you
| > recieve the mail in your vm init file and restart emacs, then, in VM,
| > open the 'folder' and auto-archive the messages. You should see the
| > blur.
|
| Nice trick! I tried it and it is working fine for me. Make sure that
| you are using revision 957 from the trunk. 'bzr log -l1' can tell you
| the verison number.
|
| > I'm assuming it's how you use VM that prevents you from using
| > auto-archive. That makes testing just a matter of temporarily
| > commenting out lines.
|
| Actually, I use the auto-folder-alist to determine the folder for
| manual saving. If I use it to auto-archive, huge amount of junk from
| my INBOX will get saved in tons of folders, which will be hard to
| clean up later on.
|
| Cheers,
| Uday
|
| --
| auto-archive messages cluttered
| https://bugs.launchpad.net/bugs/633532
| You received this bug notification because you are a direct subscriber
| of the bug.
|
| Status in VM (View Mail) for Emacs: Fix Committed
|
| Bug description:
| When I use auto-archive to save a bunch of messages from my inbox to the places listed in my auto-archive-alist, I get an annoying mess in the minibuffer:
|
| 24 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 25 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 26 archived, still working...
| Retrieving message body... done
| 1 message saved to /Users/bar/mail/python
| 27 archived, still working...
|
| which just looks like a blur at the speed at which vm works.
| What happened to the old way? It was like this:
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| 27 archived, still working...
| (pretend incrementation, there)
| so that one would see the numbers change in the minibuffer... much more informative and less scary. =)
|
| To unsubscribe from this bug, go to:
| https://bugs.launchpad.net/vm/+bug/633532/+subscribe

--

Uday Reddy (reddyuday)
tags: added: 8.0
Uday Reddy (reddyuday)
Changed in vm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.