From: Richard Stallman <rms@gnu.org>
To: Ryan Hodges <rphodges@gmail.com>
Cc: eliz@gnu.org, 67185@debbugs.gnu.org
Subject: bug#67185: Small bug in the Introduction to Elisp manual
Date: Thu, 16 Nov 2023 22:56:29 -0500 [thread overview]
Message-ID: <E1r3py1-0000OG-3T@fencepost.gnu.org> (raw)
In-Reply-To: <CABPno9LyuE-8XY7T_1PrCghx4uQGjvJCMgZTf-kwUnnbdJ5CLg@mail.gmail.com> (message from Ryan Hodges on Wed, 15 Nov 2023 12:18:23 -0800)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
We should use logical terms such as "converse" only in the strictly correct
logical sense. "Converse" is not correct here.
"Inverse" also has a specific mathematical meaning, which doesn't fit
here.
What should se use here? I think "opposite" is the best word.
> > > "The ‘kill-region’ function definition also has an ‘unless’ macro; it
> > > is the opposite of ‘when’.
If people are asking me to review more of the text, would someone please
send me the entire passage I whoudl review?
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2023-11-17 3:56 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 [this message]
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
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=E1r3py1-0000OG-3T@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=67185@debbugs.gnu.org \
--cc=eliz@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.