From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 47054@debbugs.gnu.org
Subject: bug#47054: Interlink docstrings of ‘delete’ and ‘remove’
Date: Thu, 11 Mar 2021 21:08:52 +0200 [thread overview]
Message-ID: <87o8fpik3f.fsf@mail.linkov.net> (raw)
In-Reply-To: <87h7lhir78.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 11 Mar 2021 17:35:23 +0100")
tags 47054 fixed
close 47054 28.0.50
quit
>> Shouldn't docstrings of ‘delete’ and ‘remove’ do the same
>> and refer each other?
>
> I think they should. In general, function docstrings mention related
> functions too little, I think.
To not increase entropy, I copied the same text from delq/remq
to delete/remove docstrings.
prev parent reply other threads:[~2021-03-11 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 17:12 bug#47054: Interlink docstrings of ‘delete’ and ‘remove’ Juri Linkov
2021-03-11 16:35 ` Lars Ingebrigtsen
2021-03-11 19:08 ` Juri Linkov [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=87o8fpik3f.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=47054@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).