From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 42323@debbugs.gnu.org
Subject: bug#42323: 26.3; Doc string of `seq-map'
Date: Wed, 09 Dec 2020 17:11:32 +0100 [thread overview]
Message-ID: <87y2i7x8ln.fsf@web.de> (raw)
In-Reply-To: <87ft4f3xll.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 09 Dec 2020 14:41:58 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> It is, indeed, pretty obscure. Like Drew, I wonder -- do we really
> have to put these implementation details in the doc string at all?
> Opinions?
[ Such things were often knitted with hot needle by Stefan, left for us
as "an exercise", to formulate positive ]
Details: yes, it's good to have a list of implementations. Obscure:
No. The generated doc of implementations is indeed rather obscure.
Needs a good heart to fix:
> Implementations:
>
> #'(sequence sequence) in ‘seq.el’.
^^^^^^^^^^^^^^^^^^^^^
What syntax is that actually? An accident?
> Undocumented
I would remove "Undocumented", it makes the text rather unreadable when
repeated often.
> #'sequence in ‘seq.el’.
>
> Undocumented
I wonder to what that is actually referring to. There is only one
implementation in seq.el...?
Regards,
Michael.
next prev parent reply other threads:[~2020-12-09 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 16:01 bug#42323: 26.3; Doc string of `seq-map' Drew Adams
2020-12-09 13:41 ` Lars Ingebrigtsen
2020-12-09 16:11 ` Michael Heerdegen [this message]
2020-12-09 16:44 ` Lars Ingebrigtsen
2020-12-09 19:24 ` Michael Heerdegen
2020-12-09 20:00 ` Drew Adams
2020-12-09 20:19 ` Lars Ingebrigtsen
2021-09-25 15:25 ` Stefan Kangas
2021-09-25 16:10 ` bug#42323: [External] : " Drew Adams
2021-09-25 16:21 ` Eli Zaretskii
2021-09-25 16:43 ` Stefan Kangas
2021-09-25 16:28 ` 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=87y2i7x8ln.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=42323@debbugs.gnu.org \
--cc=larsi@gnus.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.