unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 61293@debbugs.gnu.org
Subject: bug#61293: 30.0.50; [FR] Add `proper-list-p' and `plistp' to 2.7 Type Predicates section of the manual
Date: Sun, 05 Feb 2023 15:02:05 +0200	[thread overview]
Message-ID: <83357ks1te.fsf@gnu.org> (raw)
In-Reply-To: <871qn4e1fr.fsf@localhost> (message from Ihor Radchenko on Sun, 05 Feb 2023 12:34:00 +0000)

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: 61293@debbugs.gnu.org
> Date: Sun, 05 Feb 2023 12:34:00 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > proper-list-p was already documented.  I added plistp.
> 
> Thanks! Note that `proper-list-p' is not listed in section 2.7.

I don't think this should bother us.  If you type "i proper list RET",
you will land in the node which describes that term; the very next
section documents proper-list-p.  So I think everything here is fine.

> >> Also, what about `alistp'? Would it make sense to add such function?
> >
> > I don't know.  When would it be useful?
> 
> I mostly expected it is exist, but it does not.
> Also, there is `nested-alist-p'. So, not having `alistp' feels awkward.

Most probably because no one needed it, at least not too frequently.





  reply	other threads:[~2023-02-05 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05 12:01 bug#61293: 30.0.50; [FR] Add `proper-list-p' and `plistp' to 2.7 Type Predicates section of the manual Ihor Radchenko
2023-02-05 12:11 ` Eli Zaretskii
2023-02-05 12:34   ` Ihor Radchenko
2023-02-05 13:02     ` Eli Zaretskii [this message]
2023-02-06  9:20       ` Robert Pluim
2023-02-06 10:19         ` Ihor Radchenko
2023-02-06 10:43           ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-06 14:21       ` Ihor Radchenko

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=83357ks1te.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61293@debbugs.gnu.org \
    --cc=yantar92@posteo.net \
    /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).