Re: Docstring of `decode-coding-string' a bit misleading about insertion in buffer

[Kenichi Handa <handa@m17n.org>]

In article <f7ccd24b0810170719k3d743191na6c059938cf59c2@mail.gmail.com>, "Juanma Barranquero" <lekktu@gmail.com> writes:

> That's not a bug, I think, because decode-coding-string's docstring
> says nothing about the point:

>  Optional fourth arg buffer non-nil means that the decoded text is
>  inserted in buffer instead of returned as a string.  In this case,
>  the return value is the length of the decoded text.

> And I can see how decode-coding-string parallels decode-coding-region,
> where the decoded text replaces the original text without moving the
> point.

> However, the use of "inserted" in the docstring is a bit misleading,
> as `insert' does move the point. I know that "inserted" here does not
> mean that `insert' is used, but still it led me astray for a while.

How about adding "(after point and markers)" after "inserted
in buffer"?

---
Kenichi Handa
handa@ni.aist.go.jp