From: Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 59286@debbugs.gnu.org, "Rudolf Adamkovič" <salutis@me.com>
Subject: bug#59286: Documentation for seq-count
Date: Wed, 16 Nov 2022 18:50:41 +0000 [thread overview]
Message-ID: <4JV1rKTt-yUtH3mYvGuGtGDiCuWoVlTNakIzeJ1KcNeAJH3NbISV8VqQw0YDOLfmR1dCU54bdX3Tg9_YGx6kfpI34c5gtJ6SJI8bu-Bwhm4=@protonmail.com> (raw)
In-Reply-To: <8a927541-93b8-1a44-43df-77251280ffbe@gmail.com>
------- Original Message -------
On Wednesday, November 16th, 2022 at 6:09 PM, Jim Porter <jporterbugs@gmail.com> wrote:
> On 11/16/2022 9:59 AM, Heime via Bug reports for GNU Emacs, the Swiss
> army knife of text editors wrote:
>
> > Fine, but how do you use that? No information, no example. Seems to me that
> > authors of documentation willfully avoid showing examples or where to find them.
>
>
> In a Help buffer, just below the docstring is this message:
>
> Other relevant functions are documented in the sequence group.
>
> Clicking on "sequence" takes you to shortdocs, which shows an example:
>
> (seq-count #'numberp '(1 b c 4))
> ⇒ 2
>
> Maybe the "Other relevant functions" wording could be improved so that
> it's clearer though. It doesn't really indicate that you'll find more
> details about 'seq-count' in particular, just "other relevant
> functions". Something like, "See the sequence group for more
> information on this and other relevant functions," maybe?
It also says "Undocumented" at the end. Documentation is not as
helpful as many people think they are.
next prev parent reply other threads:[~2022-11-16 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 16:18 bug#59286: Documentation for seq-count Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-16 17:18 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-16 17:59 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-16 18:09 ` Jim Porter
2022-11-16 18:50 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-11-16 19:51 ` Eli Zaretskii
2022-11-16 19:40 ` Eli Zaretskii
2023-09-10 19:31 ` 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
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='4JV1rKTt-yUtH3mYvGuGtGDiCuWoVlTNakIzeJ1KcNeAJH3NbISV8VqQw0YDOLfmR1dCU54bdX3Tg9_YGx6kfpI34c5gtJ6SJI8bu-Bwhm4=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=59286@debbugs.gnu.org \
--cc=heimeborgia@protonmail.com \
--cc=jporterbugs@gmail.com \
--cc=salutis@me.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).