From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: moasenwood@zoho.eu, 35163@debbugs.gnu.org
Subject: bug#35163: 25.1; `narrow-to-region' docstring no mention of args
Date: Tue, 09 Apr 2019 09:54:27 +0300 [thread overview]
Message-ID: <83o95f7joc.fsf@gnu.org> (raw)
In-Reply-To: <87a7h0cf7p.fsf@tcd.ie> (contovob@tcd.ie)
> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Date: Mon, 08 Apr 2019 23:19:38 +0100
> Cc: 35163@debbugs.gnu.org
>
> >> could save everyone a lot of time by
> >> sending patches.)
> >
> > Should I interpret this as "one shouldn't
> > bother the maintainers with details like this"?
>
> Not at all. Eli (amongst several other fastidious contributors) keeps
> himself very busy co-maintaining Emacs, yet he still manages to set a
> stellar example of how documentation should be maintained.
>
> I'm sure what Glenn and Eli meant is closer to "a patch speaks a
> thousand words," i.e. it's easier and more efficient to convey one's
> intentions by showing, rather than describing, them, especially over the
> lossy communication medium that is email.
That is true, but a clear and concrete description of the problem,
quoting the relevant parts of the current documentation, is a great
help, even if it is accompanied by a patch. Maintaining documentation
frequently requires judgment calls, so a clear idea of the motivation
for the bug report/patch will make the report handling much more
efficient and free from misunderstandings.
next prev parent reply other threads:[~2019-04-09 6:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 18:51 bug#35163: 25.1; `narrow-to-region' docstring no mention of args Emanuel Berg
2019-04-05 19:08 ` Eli Zaretskii
2019-04-05 19:26 ` Emanuel Berg
2019-04-06 6:25 ` Eli Zaretskii
2019-04-06 7:10 ` Emanuel Berg
2019-04-06 9:01 ` Eli Zaretskii
2019-04-06 14:32 ` Emanuel Berg
2019-04-08 16:24 ` Glenn Morris
2019-04-08 16:55 ` Eli Zaretskii
2019-04-08 21:14 ` Emanuel Berg
2019-04-08 22:19 ` Basil L. Contovounesios
2019-04-09 0:45 ` Emanuel Berg
2019-04-09 1:09 ` Emanuel Berg
2019-04-09 1:13 ` Basil L. Contovounesios
2019-04-09 8:53 ` Emanuel Berg
2019-04-09 9:37 ` Robert Pluim
2019-04-09 9:55 ` Emanuel Berg
2019-04-09 11:42 ` Robert Pluim
2019-04-09 12:48 ` Emanuel Berg
2019-04-11 9:46 ` Robert Pluim
2019-04-12 5:27 ` Emanuel Berg
2019-04-09 6:54 ` Eli Zaretskii [this message]
[not found] ` <handler.35163.D35163.155474252232285.notifdone@debbugs.gnu.org>
2019-04-08 23:09 ` Noam Postavsky
2019-04-09 0:48 ` Emanuel Berg
2019-04-09 7:08 ` Eli Zaretskii
2019-04-09 6:56 ` 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=83o95f7joc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35163@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=moasenwood@zoho.eu \
/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).