From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: rphodges@gmail.com, 67185-done@debbugs.gnu.org
Subject: bug#67185: Small bug in the Introduction to Elisp manual
Date: Sun, 19 Nov 2023 12:16:13 +0200 [thread overview]
Message-ID: <834jhikpzm.fsf@gnu.org> (raw)
In-Reply-To: <E1r4Yfr-0006gM-O5@fencepost.gnu.org> (message from Richard Stallman on Sat, 18 Nov 2023 22:40:43 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: rphodges@gmail.com, 67185@debbugs.gnu.org
> Date: Sat, 18 Nov 2023 22:40:43 -0500
>
> > That manual uses "converse" and "conversely" about half a dozen times:
> > are all of them incorrect, and actually mean "opposite" or maybe "by
> > contrast"?
>
> I checked these, and I think they are correct. Each one is about reversing
> the direction of some relation, and "converse" means that/
>
> > The @code{kill-region} function definition also has an @code{unless}
> > macro; it is the converse of @code{when}.
>
> That should say "opposite". It's opposite because in the situation
> where `when' runs its body, `unless' does not run its body.
>
> The @code{unless} macro is
> > an @code{if} without a then clause
>
> The point is valid if understood in a figurative sense -- so the
> words need to indicate it is meant figuratively, not literally. How
> to do that? Maybe this:
>
> The @code{unless} macro is
> like an @code{if} except that it has no then-clause, and it supplies
> an implicit @code{nil} for that.
Thanks, I fixed these two places as you suggested, and I'm therefore
closing this bug.
next prev parent reply other threads:[~2023-11-19 10:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 23:14 bug#67185: Small bug in the Introduction to Elisp manual Ryan Hodges
2023-11-15 12:18 ` Eli Zaretskii
[not found] ` <CABPno9+==Vp-x851SLp6m7E8-e2kr7DAxkzaYC2HF7VjAk2QjQ@mail.gmail.com>
2023-11-15 19:32 ` Eli Zaretskii
2023-11-15 20:18 ` Ryan Hodges
2023-11-17 3:56 ` Richard Stallman
2023-11-17 7:19 ` Eli Zaretskii
2023-11-17 13:22 ` Ryan Hodges
2023-11-19 3:40 ` Richard Stallman
2023-11-19 10:16 ` Eli Zaretskii [this message]
2023-11-19 19:01 ` Ryan Hodges
2023-11-21 2:42 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834jhikpzm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67185-done@debbugs.gnu.org \
--cc=rms@gnu.org \
--cc=rphodges@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.