Re: header-sensitive beginning-of-line?

[Benjamin Rutt <rutt+news@cis.ohio-state.edu>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

>> Done.

Super!  It's great to find an idea that you were pondering while you
were going to bed get implemented while you were sleeping! :) Glad to
see that others felt the same way.  Thanks for your work on this, and
for everyone else's support and code.

> Oh, boy, such a simple change and so much time.  I'm sorry for the
> flurry of commits.  I hope everything works now.  Please holler if I
> missed something.

I think there may be an issue still with multi-line headers.  For
example, go to any multiline references header and type C-a and you
get the following stack trace:

Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
  message-beginning-of-line(1)
  call-interactively(message-beginning-of-line)

Also, if you are on the line that looks like

"--text follows this line--"

there is the same problem.

The following patch to cvs should fix it (sorry for the diff -c but
the version of diff on my solaris machine doesn't support diff
-u...will have to install GNU diff):

*** message.el.~6.153.~	Fri Nov  9 09:40:34 2001
--- message.el	Fri Nov  9 10:18:07 2001
***************
*** 3973,3979 ****
  	     (eoh (re-search-forward ": *" eol t)))
  	(if (equal here eoh)
  	    (goto-char bol)
! 	  (goto-char eoh)))
      (beginning-of-line n)))
  
  (defun message-buffer-name (type &optional to group)
--- 3973,3981 ----
  	     (eoh (re-search-forward ": *" eol t)))
  	(if (equal here eoh)
  	    (goto-char bol)
! 	  (if eoh
! 	      (goto-char eoh)
! 	    (beginning-of-line n))))
      (beginning-of-line n)))
  
  (defun message-buffer-name (type &optional to group)

Thanks again,
-- 
Benjamin