GNU bug report logs -
#67185
Small bug in the Introduction to Elisp manual
Previous Next
Reported by: Ryan Hodges <rphodges <at> gmail.com>
Date: Wed, 15 Nov 2023 01:58:03 UTC
Severity: normal
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #34 received at 67185-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Thank you both. After I finish learning Elisp, I hope I can make some real
contributions.
Cheers,
Ryan Hodges
On Sun, Nov 19, 2023 at 2:16 AM Eli Zaretskii <eliz <at> gnu.org> wrote:
> > From: Richard Stallman <rms <at> gnu.org>
> > Cc: rphodges <at> gmail.com, 67185 <at> 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.
>
[Message part 2 (text/html, inline)]
This bug report was last modified 1 year and 185 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.