VM

Comment 1 for bug 916695

Revision history for this message

Uday Reddy (reddyuday) wrote on 2012-01-15: Re: [Bug 916695] [NEW] vm-follow-summary-cursor

mere user writes:

> Public bug reported:
>
> hi Uday, using the latest cvs version, when looking to my outgoing mail
> folder, I get this:
>
> Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
> vm-follow-summary-cursor()
> vm-scroll-forward(nil)
> call-interactively(vm-scroll-forward nil nil)
>
> let me know if you need a more detailed, reproducible report; I noticed
> that these abbreviated ones are typically sufficient for you to see what
> the problem is. :-)

Not really. It might seem like I know what is happening already. That is
usually because I observed the same issue myself or because I made some
changes which I expect might have some funny effects like that.

In this case, we might need to sweat a bit because it is not an easy to problem
to track down. Summary problems are hard to figure out because they are
based on cached data. If for any reason the cached data becomes faulty, the
results are likely to show up in handling the summary. But the root
problems might have been somewhere else.

The first thing to do is to load the uncompiled version of the file that
gave the error. In this case, if you do

C-h f vm-follow-summary-cursor

it tells you that it comes from vm-motion. So, if you

M-x load-library RET vm-motion.el

we would get a better error trace.

The second thing to do would be to identify which revision introduced the
error. If you go to the vm build directory and do

bzr log -l5

it shows the last 5 revisions. (Or, whichever number you specify.) Then if
you can think back and identify what was the last good revision you used,
that will give me some handle on where to look. In this case, the revision
1334 was a major revision, which added new fields to the cached data. So, I
am guessing that the revision 1333 might be good for you and 1334 might
break.

bzr revert -rNNNN

backtracks your VM to an older revision NNNN.

Can you try those please? I will be going (coming?) to the US on Friday and
will be away from VM for at least a week. So, it will be good if we can
track this down today.

Cheers,
Uday

mere user writes:

> Public bug reported:
> 
> hi Uday, using the latest cvs version, when looking to my outgoing mail
> folder, I get this:
> 
> Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
>   vm-follow-summary-cursor()
>   vm-scroll-forward(nil)
>   call-interactively(vm-scroll-forward nil nil)
> 
> let me know if you need a more detailed, reproducible report; I noticed
> that these abbreviated ones are typically sufficient for you to see what
> the problem is.  :-)

Not really.  It might seem like I know what is happening already.  That is
usually because I observed the same issue myself or because I made some
changes which I expect might have some funny effects like that.

In this case, we might need to sweat a bit because it is not an easy to problem
to track down.  Summary problems are hard to figure out because they are
based on cached data.  If for any reason the cached data becomes faulty, the
results are likely to show up in handling the summary.  But the root
problems might have been somewhere else.

The first thing to do is to load the uncompiled version of the file that
gave the error.  In this case, if you do

C-h f vm-follow-summary-cursor

it tells you that it comes from vm-motion.  So, if you

M-x load-library RET vm-motion.el

we would get a better error trace.

The second thing to do would be to identify which revision introduced the
error.  If you go to the vm build directory and do

bzr log -l5

it shows the last 5 revisions.  (Or, whichever number you specify.)  Then if
you can think back and identify what was the last good revision you used,
that will give me some handle on where to look.  In this case, the revision
1334 was a major revision, which added new fields to the cached data.  So, I
am guessing that the revision 1333 might be good for you and 1334 might
break.

bzr revert -rNNNN

backtracks your VM to an older revision NNNN.

Can you try those please?  I will be going (coming?) to the US on Friday and
will be away from VM for at least a week.  So, it will be good if we can
track this down today.

Cheers,
Uday