From: Jim Porter <jporterbugs@gmail.com>
To: Heime <heimeborgia@protonmail.com>, "Rudolf Adamkovič" <salutis@me.com>
Cc: 59286@debbugs.gnu.org
Subject: bug#59286: Documentation for seq-count
Date: Wed, 16 Nov 2022 10:09:39 -0800 [thread overview]
Message-ID: <8a927541-93b8-1a44-43df-77251280ffbe@gmail.com> (raw)
In-Reply-To: <HUo_Z418gLLWcmn0H-GBPcipq5QA5LEBYgw-ynGhzJ0VFVkVvpCDJwMC3gx0lNdtVY_s9WL0VgirrrtJ6w49V3Gj3DeeEKyeaIaBBS81bCo=@protonmail.com>
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?
next prev parent reply other threads:[~2022-11-16 18:09 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 [this message]
2022-11-16 18:50 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=8a927541-93b8-1a44-43df-77251280ffbe@gmail.com \
--to=jporterbugs@gmail.com \
--cc=59286@debbugs.gnu.org \
--cc=heimeborgia@protonmail.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).