Re: Mysterious fontification/C++ context issue

[martin rudalics]

>     6. In any case, the new behavior should be documented since it applies
>     whenever `open-paren-in-column-0-is-defun-start' is set to nil.
>
> Where are documentation changes are needed for this?

In the Elisp description of `beginning-of-defun' I presume.  I'd explain
the following issues:

1. `beginning-of-defun' moves to the beginning of the line where it
expects the beginning of a defun.  That position is not necessarily part
of that defun and maybe not even at the "outermost" level as I explained
in the example of point 2 of my previous mail.  This was a non-issue
when searching for an open paren in column zero (think of a couple of
parenthesized expressions on the same line).

2. That a user's idea of "defun" for her programming language does not
necessarily coincide with that of `beginning-of-defun'.

foo (...)
...
{
...
}

will now get you two defuns instead of one.  This should be explained
for C mode at least.