Subject: bug#31325: 27.0.50; PROPOSAL: introduce a new function to recenter without redisplaying the frame

From: Robert Pluim <[email-masked]>
Date: Tue, 03 Jul 2018 10:49:49 +0200

John Shahid <[email-masked]> writes:

> Eli Zaretskii <[email-masked]> writes:
>>
>>> --- a/doc/lispref/windows.texi
>>> +++ b/doc/lispref/windows.texi
>>> @@ -4154,7 +4154,8 @@ Textual Scrolling
>>>  @code{recenter} puts the line containing point in the middle of the
>>>  window.  If @var{count} is @code{nil} and @var{redisplay} is
>>>  non-@code{nil}, this function may redraw the frame, according to the
>>> -value of @code{recenter-redisplay}.
>>> +value of @code{recenter-redisplay}. Interactive calls pass non-‘nil’
>>> +for @var{redisplay}.              ^^
>>
>> Two spaces between sentences.
>
> Sorry about that, I'm still getting used to using 2 spaces after
> period. How do you spot these ? Do you have some font-lock keyword to
> highlight them. I found checkdoc not to be very useful for checking the
> manual or docstrings in .c files.

You get used to it. One way to check is to put point at the beginning
of the text you changed and seeing if 'M-e' (forward-sentence) does
the expected thing.

Robert