From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 42835@debbugs.gnu.org
Subject: bug#42835: 26.3; Doc of `cl-' functions, (cl) Naming Conventions
Date: Wed, 9 Dec 2020 08:27:46 -0800 (PST) [thread overview]
Message-ID: <9534f420-6782-419c-a124-8106f7ea7ca1@default> (raw)
In-Reply-To: <87pn3j3xyl.fsf@gnus.org>
> > This node has a list of functions and macros, some of which have
> > footnotes. I don't understand the footnotes (which are not
> > sentences, BTW). For example, `cl-incf' has footnote [1], which says:
> > [1] Only when PLACE is a plain variable name.
>
> This is modifying the statement before the table:
>
> ---
> The following simple functions and macros are defined in
> @file{cl-lib.el}; they do not cause other components like
> @file{cl-extra} to be loaded.
> ---
Still not clear. They are defined in cl-lib only when
PLACE is a var name? They don't cause other components
to be loaded only when PLACE is a var name?
> > Similarly for the other names and their footnotes.
>
> Same for them.
It's not clear to me whether you've fixed the doc or are
just trying to explain it to me. If the latter then this
is, I guess, a "won't fix". (It needs to be fixed.)
> > The manual entry for `cl-pushnew' is even worse. It talks only about
> > `eql' and doesn't say anything about :test. There's an xref to node
> > `Lists as Sets' for info about the keyword args, but that node also
> > says nothing about :test. Instead, that node just punts further, to
> > node `Sequences'.
>
> I've now removed the eql claim, and punted the explanation for :test to
> "Lists as Sets".
Dunno what that means. Does it mean that `Lists as Sets'
has been updated to cover the keyword args, including
:test?
prev parent reply other threads:[~2020-12-09 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 20:18 bug#42835: 26.3; Doc of `cl-' functions, (cl) Naming Conventions Drew Adams
2020-12-09 13:34 ` Lars Ingebrigtsen
2020-12-09 16:27 ` Drew Adams [this message]
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=9534f420-6782-419c-a124-8106f7ea7ca1@default \
--to=drew.adams@oracle.com \
--cc=42835@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 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).