From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
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:56:39 +0300 [thread overview]
Message-ID: <83mukz7jko.fsf@gnu.org> (raw)
In-Reply-To: <87d0lwccwc.fsf_-_@gmail.com> (message from Noam Postavsky on Mon, 08 Apr 2019 19:09:39 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Date: Mon, 08 Apr 2019 19:09:39 -0400
> Cc: , Emanuel Berg <moasenwood@zoho.eu>
>
> > Or at least a clear description of the problem.
>
> To be fair, message [11] is fairly clear and pretty close to what Glenn
> wrote (perhaps it misses the emphasis on satisfying checkdoc).
Obviously, it wasn't clear enough to me, or I wouldn't have asked the
follow-up questions. When it became clear, I pushed a change within
minutes.
> Things unfortunately derailed after that.
>
> An 80+ line elisp riddle on a report about a docstring bug is surely a
> sign something has gone horribly wrong...
Indeed.
prev parent reply other threads:[~2019-04-09 6:56 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
[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 [this message]
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=83mukz7jko.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35163@debbugs.gnu.org \
--cc=moasenwood@zoho.eu \
--cc=npostavs@gmail.com \
/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.