From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50731@debbugs.gnu.org
Subject: bug#50731: `progress-reporter-update' docstring and `backward-sexp' interaction
Date: Thu, 23 Sep 2021 00:12:08 -0700 [thread overview]
Message-ID: <CADwFkmksoemh-rffc+1Dyh_pYuspfbEV4WUb=P5-MW-F7Q4jYQ@mail.gmail.com> (raw)
In-Reply-To: <83v92rvmsr.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> How do we decide? What is TRT for backward-sexp in context that has
> no sexps? If we change anything here, it could potentially affect a
> lot of unrelated code out there.
That's true.
> Once again, why does checkdoc want you to have 2 spaces there? what
> rule is it that ends up requiring that?
Sorry, I didn't understand you were asking about checkdoc. The code
there is really simple: find the next dot (that is also at a word
boundary), run `backward-sexp', use a regexp to see if this is an
abbreviation.
So it lands on the "r" in "reporter---i.e." and says, no, this is not an
abbreviation I know about, so there has to be two spaces after the dot.
next prev parent reply other threads:[~2021-09-23 7:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 6:52 bug#50731: `progress-reporter-update' docstring and `backward-sexp' interaction Stefan Kangas
2021-09-22 7:37 ` Eli Zaretskii
2021-09-22 22:12 ` Stefan Kangas
2021-09-23 6:16 ` Eli Zaretskii
2021-09-23 7:12 ` Stefan Kangas [this message]
2021-09-23 7:47 ` Eli Zaretskii
2021-09-23 9:04 ` Stefan Kangas
2021-09-23 20:40 ` Stefan Kangas
2021-09-22 20:35 ` Lars Ingebrigtsen
2021-09-22 22:12 ` Stefan Kangas
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='CADwFkmksoemh-rffc+1Dyh_pYuspfbEV4WUb=P5-MW-F7Q4jYQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=50731@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).