From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 41026@debbugs.gnu.org
Subject: bug#41026: Improve documentation of `makunbound' and `fmakunbound'
Date: Sat, 02 May 2020 16:17:04 +0200 [thread overview]
Message-ID: <87pnbm4e1r.fsf@stefankangas.se> (raw)
In-Reply-To: <83sggisacb.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 02 May 2020 17:03:16 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stefan Kangas <stefan@marxist.se>
>> Date: Sat, 2 May 2020 15:53:37 +0200
>>
>> DEFUN ("makunbound", Fmakunbound, Smakunbound, 1, 1, 0,
>> - doc: /* Make SYMBOL's value be void.
>> -Return SYMBOL. */)
>> + doc: /* Make variable SYMBOL's value be void.
>> +Return SYMBOL.
>> +
>> +For more information, see Info node `(elisp) Void Variables'.
>> +
>> +The corresponding operation for functions is `fmakunbound'. */)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> The "corresponding" part isn't accurate, is it?
Sorry, I thought it was. But my understanding of this is probably
much too naive.
Would we avoid the inaccuracy by deleting the word "corresponding"?
Thank you for reviewing.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-05-02 14:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 13:53 bug#41026: Improve documentation of `makunbound' and `fmakunbound' Stefan Kangas
2020-05-02 14:03 ` Eli Zaretskii
2020-05-02 14:17 ` Stefan Kangas [this message]
2020-05-02 14:22 ` Eli Zaretskii
2020-05-02 20:25 ` Stefan Kangas
2020-05-02 21:12 ` Andreas Schwab
2020-05-02 21:30 ` Stefan Kangas
2020-05-04 3:06 ` Richard Stallman
2020-05-04 7:31 ` Andreas Schwab
2020-05-04 12:52 ` Stefan Kangas
2020-05-04 13:05 ` Andreas Schwab
2020-05-03 14:21 ` Eli Zaretskii
2020-05-03 20:07 ` Stefan Kangas
2020-05-02 14:55 ` Andreas Schwab
2020-05-02 15:00 ` Stefan Kangas
2020-05-02 15:41 ` Eli Zaretskii
2020-05-02 20:22 ` Drew Adams
2020-05-03 3:43 ` Richard Stallman
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=87pnbm4e1r.fsf@stefankangas.se \
--to=stefan@marxist.se \
--cc=41026@debbugs.gnu.org \
--cc=eliz@gnu.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).