unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Xiyue Deng <manphiz@gmail.com>
Cc: 67577-done@debbugs.gnu.org
Subject: bug#67577: 29.1; Comments in kill-region seem to explain unless wrong
Date: Sun, 03 Dec 2023 08:32:49 +0200	[thread overview]
Message-ID: <83wmtv7q3y.fsf@gnu.org> (raw)
In-Reply-To: <87y1ec87gx.fsf@debian-hx90.lan> (message from Xiyue Deng on Sat,  02 Dec 2023 16:17:50 -0800)

> From: Xiyue Deng <manphiz@gmail.com>
> Cc: 67577@debbugs.gnu.org
> Date: Sat, 02 Dec 2023 16:17:50 -0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Xiyue Deng <manphiz@gmail.com>
> >> Cc: 67577@debbugs.gnu.org
> >> Date: Sat, 02 Dec 2023 01:21:37 -0800
> >> 
> >> 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.
> >
> > Sorry, I don't understand: what is the problem with the current text?
> > 'when' is NOT 'if' without 'then', it's 'if' without 'else'..
> >
> 
> Ah looks like I miss understood.  Sorry for the confusion.  Please feel
> free to close.

Done.





      reply	other threads:[~2023-12-03  6:32 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
2023-12-02 12:36     ` Eli Zaretskii
2023-12-03  0:17       ` Xiyue Deng
2023-12-03  6:32         ` Eli Zaretskii [this message]

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=83wmtv7q3y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=67577-done@debbugs.gnu.org \
    --cc=manphiz@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 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).