bug#23046: 25.0.92; Docstring of `sh-indent-after-continuation' lacks backslash escapes

[npostavs@users.sourceforge.net]

tags 23046 fixed
close 23046 25.1
quit

Philipp Stephani <p.stephani2@gmail.com> writes:

> M-x load-library RET sh-script RET
> C-h v sh-indent-after-continuation
>
> prints
>
> ...
> If non-nil, indent relative to the continued line’s beginning.
> Continued lines can either be indented as "one long wrapped line" without
> paying attention to the actual syntactic structure, as in:
>
>    for f        in a; do        toto;        done
>
> or as lines that just don’t have implicit semi-colons between them, as in:
>
>    for f    in a; do        toto;    done
>
> With ‘always’ you get the former behavior whereas with nil you get the latter.
> With t, you get the latter as long as that would indent the continuation line
> deeper than the initial line.
> ...
>
> I think the code examples were meant to be on multiple lines.  For that
> the backslashes in the docstring need to be escaped.

Yep, looks like a copy-pasto, fixed in 113d1e2.