From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 2475687: Improve documentation changes of a recent commit
Date: Mon, 15 Apr 2019 17:57:01 +0300 [thread overview]
Message-ID: <83ftqjiaf6.fsf@gnu.org> (raw)
In-Reply-To: <09715d71-19d0-fe94-f819-581e89078d84@yandex.ru> (message from Dmitry Gutov on Sun, 14 Apr 2019 23:34:25 +0300)
> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sun, 14 Apr 2019 23:34:25 +0300
>
> On 14.04.2019 17:40, Eli Zaretskii wrote:
>
> > Yes, you've said that in the past, and I think we agreed to disagree
> > on it. My opinion is that it's a judgment call: sometimes duplication
> > is for the better, and sometimes for the worse.
>
> I hope you are taking in consideration the increased overhead of
> maintaining it when adding further changes to either of these functions.
I did. We have enough similar doc strings already; one more or less
won't change anything.
> > Especially for a function
> > whose name doesn't necessarily speak volumes about its purpose.
>
> Which of the two functions? Both of them seem to have pretty apt names.
Not IMO. "Parse" is ambiguous, and doesn't hint on the fact that
these functions produce a Lisp representation of a JSON object.
> > Doesn't sound like something I'd say, not to that effect. "Allowed",
> > yes; but not "required".
>
> Even if it said "Allowed", I'd interpret it like "I'm allowed to
> structure the documentation this way, without expecting somebody else to
> come later and rewrite it with increased duplication".
Please don't take my changes as some kind of indirect accusation
against you. It was just a routine maintenance job, something I do
almost every day when I see documentation that can be improved.
> > If anything, it is easier to refer to a
> > previous function in the manual, when two or more functions are
> > described one after another. By contrast, doc strings are never
> > "near" one another.
>
> When one references another? It's always fast for the user to navigate
> to the other docstring.
It's at least one more keystroke. More importantly, the doc strings
are slightly different, because some of the things one function does
make no sense for the other. So the reader will also have to decide
which parts are not relevant.
next prev parent reply other threads:[~2019-04-15 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190413070933.31645.83730@vcs0.savannah.gnu.org>
[not found] ` <20190413070934.DDF7B202C6@vcs0.savannah.gnu.org>
2019-04-14 10:34 ` [Emacs-diffs] master 2475687: Improve documentation changes of a recent commit Dmitry Gutov
2019-04-14 14:40 ` Eli Zaretskii
2019-04-14 20:34 ` Dmitry Gutov
2019-04-15 14:57 ` Eli Zaretskii [this message]
2019-04-15 15:42 ` Dmitry Gutov
2019-04-15 16:06 ` Eli Zaretskii
2019-04-15 17:15 ` Dmitry Gutov
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=83ftqjiaf6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@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 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.