bug when getting new mail

[mere user]

is this sufficient to figure out what the problem might be? E
as of today in development version.

Debugger entered--Lisp error: (wrong-type-argument vectorp bonk)
  intern("<email address hidden>" bonk)
  vm-thread-subtree([[#<marker at 1 in RMAIL> ...
  vm-thread-count([[#<marker at 1 in RMAIL> ...
  byte-code("...
..." [m vm-thread-root vm-thread-count 1] 3)
  vm-thread-root-p([[#<marker at 1 in RMAIL>...
  vm-summary-faces-add([[#<marker at 1 in RMAIL> ...
  vm-do-summary(nil)
  vm-do-needed-summary-rebuild()
  #[(b) "... \"...
..." [b vm-buffers-needing-undo-boundaries ...
  mapatoms(#[(b) ...
... [b vm-buffers-needing-undo-boundaries ...
  vm-update-summary-and-mode-line()
  vm-get-spooled-mail-normal(t)
  vm-get-spooled-mail(t)
  vm-get-new-mail(nil)
  call-interactively(vm-get-new-mail nil nil)

[Uday Reddy (reddyuday)]

Hi Eli, Do you have debug-on-signal turned on? If so, you need to type `c'
to continue from spurious errors like these.

What happens if you turn off both debug-on-signal and debug-on-error?

Cheers,
Uday

[mere user (emacs-user)]

when I turn on debug on signal and error, I get this: (different error...?)

  insert-file-contents("~/.vm.windows")
  byte-code("\..." [vm-xemacs-mule-p vm-xemacs-file-coding-p
coding-system-for-read file no-conversion raw-text
insert-file-contents read] 2)
  vm-load-window-configurations("~/.vm.windows")
  vm-session-initialization()
  vm("~/RMAIL")

On Wed, May 4, 2011 at 12:30 AM, Uday Reddy wrote:
> What happens if you turn off both debug-on-signal and debug-on-error?

[Uday Reddy (reddyuday)]

mere user writes:

> when I turn on debug on signal and error, I get this: (different
> error...?)

Yes, this is a different error.

I am not sure what you are trying to find, yet!

Cheers,
Uday

[mere user (emacs-user)]

On Wed, May 4, 2011 at 9:00 AM, Uday Reddy <email address hidden> wrote:
> mere user writes:
>
>> when I turn on debug on signal and error, I get this: (different
>> error...?)
>
> Yes, this is a different error.
>
> I am not sure what you are trying to find, yet!

Hi Uday, it's just that when I use the version posted yesterday I seem
to be getting these errors. when I use an older version, things seem
to work fine. I think I did make clean etc before recompiling the new
version. is this not a bug(s) in the new revision?
Eli

[Uday Reddy (reddyuday)]

mere user writes:

> Hi Uday, it's just that when I use the version posted yesterday I seem
> to be getting these errors. when I use an older version, things seem
> to work fine. I think I did make clean etc before recompiling the new
> version. is this not a bug(s) in the new revision?

I don't get any errors at all.

Why don't you tell me exactly what error you get and in what situation?
Please don't set debug-on-error when you start with.

Cheers,
Uday

[Uday Reddy (reddyuday)]

Sorry, Eli. It turns out that I hadn't loaded the latest revision. So I
wasn't seeing the error you were.

It was a silly bug. Now fixed in revision 1209.

Cheers,
Uday

[John Hein (xpqheqdvq4)]

In my case, here's a recipe to reproduce:

Mark 5 messages
V C marked
C-t
"Wrong type argument: vectorp, bonk" shows up but the virtual folder looks fine, including proper threading.
Try to operate on a message, say:
M-x vm-set-message-attributes "read"
Same error message, and the message attribute is unchanged.

Turning on debug-on-error and doing the same gives the backtrace shown in bug 777174

[John Hein (xpqheqdvq4)]

I posted comment 7 before seeing comment 6. I'll try 1209

[Uday Reddy (reddyuday)]

John Hein writes:

> I posted comment 7 before seeing comment 6. I'll try 1209

I think it is the same issue. I didn't first understand what Eli was
running into, but your report clarified it for me. Thanks.

Uday

[John Hein (xpqheqdvq4)]

Yep. 1209 fixed it. Typos are fun!

[mere user (emacs-user)]

fixed for me too. sorry for sending a cryptic report

On Thu, May 5, 2011 at 12:28 AM, John Hein <email address hidden> wrote:
> Yep.  1209 fixed it.  Typos are fun!