From: Robert Pluim <rpluim@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: master 95e8c7d 1/2: ; Fix typos
Date: Mon, 12 Oct 2020 10:19:34 +0200 [thread overview]
Message-ID: <m2eem35015.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkm=EwV3eY7dADMf0CjsowF8=Xi0VQJEJFZPm=aovytYFdg@mail.gmail.com> (Stefan Kangas's message of "Sat, 10 Oct 2020 01:14:40 -0700")
>>>>> On Sat, 10 Oct 2020 01:14:40 -0700, Stefan Kangas <stefan@marxist.se> said:
Stefan> Eli Zaretskii <eliz@gnu.org> writes:
>>> But it is true that it would be preferable if the code matched the
>>> documentation. In the interest of consistency we are better off
>>> sticking to one spelling. Note that we already had around 40 other
>>> instances of "parsable" in our source tree.
>>
>> Since renaming symbols involves some pain, do we really need to be
>> 100% consistent here?
Stefan> I personally don't have a very strong opinion either way, FWIW.
I think I prefer consistency between the docstrings and the associated
code to global consistency, and changing code is always risky, so Iʼd
prefer if the docstrings were changed back.
Robert
--
next prev parent reply other threads:[~2020-10-12 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201009134249.15265.31644@vcs0.savannah.gnu.org>
[not found] ` <20201009134252.81B3620A15@vcs0.savannah.gnu.org>
2020-10-09 13:57 ` master 95e8c7d 1/2: ; Fix typos Robert Pluim
2020-10-09 14:40 ` Eli Zaretskii
2020-10-09 21:01 ` Stefan Kangas
2020-10-09 21:14 ` Drew Adams
2020-10-10 6:56 ` Eli Zaretskii
2020-10-10 8:14 ` Stefan Kangas
2020-10-12 8:19 ` Robert Pluim [this message]
2020-10-12 14:58 ` Eli Zaretskii
2020-10-16 9:58 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2eem35015.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefan@marxist.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.