From: Emanuel Berg <moasenwood@zoho.eu>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 35163@debbugs.gnu.org
Subject: bug#35163: 25.1; `narrow-to-region' docstring no mention of args
Date: Tue, 09 Apr 2019 02:48:39 +0200 [thread overview]
Message-ID: <86imvouhp4.fsf@zoho.eu> (raw)
In-Reply-To: <87d0lwccwc.fsf_-_@gmail.com> (Noam Postavsky's message of "Mon, 08 Apr 2019 19:09:39 -0400")
Noam Postavsky wrote:
>> 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).
I agree that message 11 is fairly clear,
however checkdoc is mentioned there as well:
"(checkdoc-current-buffer t) would tell you
this ..."
> 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...
Ha ha :D
> [11]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35163#11
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2019-04-09 0:48 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 [this message]
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=86imvouhp4.fsf@zoho.eu \
--to=moasenwood@zoho.eu \
--cc=35163@debbugs.gnu.org \
--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 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).