Re: Invalid Data on Line 1 - Please Help!

[Kevin Greiner <kgreiner@xpediantsolutions.com>]

Jake Colman <colman@ppllc.com> writes:

> I've posted this before and have not gotton back anything useful  Someone
> suggested using toggle-debug-on-error but this is not considered an elisp
> error.  It is just an error printed by gnus.
>
> This is not making any sense to me!  Everything used to work fine for years.
> Now it's crapping out quite regularly.  How can I trace down what's going on?
>  Maybe I have corruption somwhere?  How can I find it?

Jake,
Here's what I'd like you to do.

1) Eval (c-h v) load-path to see the list of directories from which
   libraries are loaded.  Look for the gnus directory.

2) Edit the gnus-util.el file in that directory.  Look for the
   gnus-parse-without-error macro.  Insert (debug) as I've shown
   below.

(defmacro gnus-parse-without-error (&rest body)
  "Allow continuing onto the next line even if an error occurs."
  `(while (not (eobp))
     (condition-case ()
	 (progn
	   ,@body
	   (goto-char (point-max)))
       (error
(debug)
	(gnus-error 4 "Invalid data on line %d"
		    (count-lines (point-min) (point)))
	(forward-line 1)))))

4) Do M-x load-library <ret>gnus-util.el<ret>
      M-x load-library <ret>nnagent.el<ret>
      M-x load-library <ret>gnus-sum.el<ret>
4) Start gnus as usual.
5) Proceed until you get thrown into the debugger.

6) While in the debugger, eval (current-buffer).  If that buffer isn't
   visible, select it so that you can see what is wrong with line 1.

7) Exit gnus, edit the broken file to fix line 1, then start gnus to
   see if you're OK.

I'd appreciate it if you'd post which file had the invalid line and
also the invalid line itself.  Gnus may not be able to avoid the error
but it should, if at all possible, handle it with more grace.

Kevin