Re: Confusing doc string of list-or-string at point

[Stefan Monnier]

>> Splitting the work between `char-after` and `char-syntax` means that we
>> can't obey any `syntax-table` text properties placed on that char.
>> So I think the above change would be a regression in this sense (tho
>> I understand it fixes or circumvents a bug elsewhere).
>
> No bugs prompted this patch, just noticed the difference between
> this function and its counterpart thing-at-point--beginning-of-sexp
> that uses `(char-syntax (char-before))`.

My point was just that `syntax-after` is almost always the better choice
over (char-syntax (char-after)) because it has access to more
information, so the better fix to unify the two would be to use
`syntax-after` in both cases ;-)


        Stefan