From: Robert Pluim <rpluim@gmail.com>
To: John Shahid <jvshahid@gmail.com>
Cc: 31325@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#31325: 27.0.50; PROPOSAL: introduce a new function to recenter without redisplaying the frame
Date: Tue, 03 Jul 2018 10:49:49 +0200 [thread overview]
Message-ID: <87d0w4d7pu.fsf@gmail.com> (raw)
In-Reply-To: <87lgatxtip.fsf@gmail.com> (John Shahid's message of "Mon, 02 Jul 2018 20:38:38 +0000")
John Shahid <jvshahid@gmail.com> writes:
> Eli Zaretskii <eliz@gnu.org> 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
next prev parent reply other threads:[~2018-07-03 8:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 0:48 bug#31325: 27.0.50; PROPOSAL: introduce a new function to recenter without redisplaying the frame John Shahid
2018-05-08 1:37 ` Stefan Monnier
2018-06-28 13:27 ` John Shahid
2018-06-30 9:45 ` Eli Zaretskii
2018-06-30 20:20 ` John Shahid
2018-07-01 9:05 ` martin rudalics
2018-07-01 13:17 ` John Shahid
2018-07-01 16:22 ` Eli Zaretskii
2018-07-01 16:54 ` John Shahid
2018-07-01 17:03 ` Eli Zaretskii
2018-07-01 17:14 ` Eli Zaretskii
2018-07-01 17:25 ` John Shahid
2018-07-01 20:17 ` Drew Adams
2018-07-01 20:56 ` John Shahid
2018-07-01 23:04 ` Drew Adams
2018-07-02 2:27 ` John Shahid
2018-07-02 15:18 ` Eli Zaretskii
2018-07-01 17:18 ` John Shahid
2018-07-01 18:05 ` Eli Zaretskii
2018-07-01 18:58 ` John Shahid
2018-07-02 15:22 ` Eli Zaretskii
2018-07-02 20:38 ` John Shahid
2018-07-03 8:49 ` Robert Pluim [this message]
2018-07-03 16:38 ` John Shahid
2018-07-07 9:09 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0w4d7pu.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=31325@debbugs.gnu.org \
--cc=jvshahid@gmail.com \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).