|Subject:||Re: Patch for beginning-of-visual-line and end-of-visual-line|
|Date:||Sat, 12 Aug 2017 09:14:47 -0400|
> From: Justin Burkett <address@hidden>
> Date: Sat, 12 Aug 2017 07:54:16 -0400
> Cc: address@hidden
> So I think this behavior is correct, perhaps we should describe this
> special case in the doc string. This function must end up at the
> beginning of a visual line, and in your case there's only one such
> place. Note that (beginning-of-visual-line 1) and
> (beginning-of-visual-line) all end up in the same place in this case.
> That's fine with me. While we're at it, move-beginning-of-line has the same inconsistency in the docstring.
I've fixed the doc strings of both these functions, thanks.
> Also, it would be nice to specify what the return value of these functions is if the docstring will change.
The return value is unspecified, and I don't think I see why we should
|[Prev in Thread]||Current Thread||[Next in Thread]|