what is the button stop between headers and message?

what is the button stop between headers and message?

[Jack Vinson]

If I TAB through a message to get to a particular button, I always get a
stop on the empty line between the headers and the message itself.  I've
got headers hidden, so I suppose there might be a stop on one of those
invisible lines.  However, when I press the button (hit return) nothing
happens -- no beep, no calls.

Is the stop there a result of the regexp?

-- 
Jack Vinson                                                  Sunderland, MA
jvinson@cheux.ecs.umass.edu    <http://www.cis.upenn.edu/~vinson/home.html>
"There's balogna in our slacks."

Re: what is the button stop between headers and message?

[Per Abrahamsen]

>>>>> "JV" == Jack Vinson <jvinson@cheux.ecs.umass.edu> writes:

JV> If I TAB through a message to get to a particular button, I always get a
JV> stop on the empty line between the headers and the message itself.  I've
JV> got headers hidden, so I suppose there might be a stop on one of those
JV> invisible lines.  However, when I press the button (hit return) nothing
JV> happens -- no beep, no calls.

There are usually several buttons in the hidden headers.  However, the
hidden headers are intangible, so point will move to the end of the
hidden headers.  At that point there are no button, so pressing `RET'
will do nothing.

I guess `gnus-article-next-button' should skip over invisible (or at
least intangible) text.