From: Xiyue Deng <manphiz@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67577@debbugs.gnu.org
Subject: bug#67577: 29.1; Comments in kill-region seem to explain unless wrong
Date: Sat, 02 Dec 2023 01:21:37 -0800 [thread overview]
Message-ID: <8734wl9cym.fsf@debian-hx90.lan> (raw)
In-Reply-To: <83r0k582r8.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 02 Dec 2023 09:47:23 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Xiyue Deng <manphiz@gmail.com>
>> Date: Fri, 01 Dec 2023 21:36:11 -0800
>>
>>
>> It says "'unless' is an 'if' without the then-part", which I think it
>> meant to say "'unless' is the inverse of 'if' ...", as I think "an 'if'
>> without the then-part" is supposed to be 'when'. Let me know if my
>> understanding is wrong. If not, please find the patch in my next post.
>
> We already fixed that part. The text now says:
>
> The ‘kill-region’ function definition also has an ‘unless’ macro; it
> is the opposite of ‘when’. The ‘unless’ macro is like an ‘if’ except
> that it has no then-clause, and it supplies an implicit ‘nil’ for that.
>
> So I don't think this needs to be fixed anymore.
Hmm, I think the comment part on latest head is still the same as last
time I checked. Please also take a look at my patch and see whether it
is still worth committing.
--
Xiyue Deng
next prev parent reply other threads:[~2023-12-02 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 5:36 bug#67577: 29.1; Comments in kill-region seem to explain unless wrong Xiyue Deng
[not found] ` <handler.67577.B.170149541415494.ack@debbugs.gnu.org>
2023-12-02 5:46 ` bug#67577: Acknowledgement (29.1; Comments in kill-region seem to explain unless wrong) Xiyue Deng
2023-12-02 7:47 ` bug#67577: 29.1; Comments in kill-region seem to explain unless wrong Eli Zaretskii
2023-12-02 9:21 ` Xiyue Deng [this message]
2023-12-02 12:36 ` Eli Zaretskii
2023-12-03 0:17 ` Xiyue Deng
2023-12-03 6:32 ` Eli Zaretskii
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=8734wl9cym.fsf@debian-hx90.lan \
--to=manphiz@gmail.com \
--cc=67577@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).