From: Noam Postavsky <npostavs@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 19208@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
Phillip Lord <phillip.lord@newcastle.ac.uk>,
Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#19208: replace-match unhelpful error message
Date: Sun, 04 Aug 2019 10:12:06 -0400 [thread overview]
Message-ID: <87ef21rpe1.fsf@gmail.com> (raw)
In-Reply-To: <m2woftfgm5.fsf@linux-m68k.org> (Andreas Schwab's message of "Sun, 04 Aug 2019 11:02:26 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
> On Aug 03 2019, Noam Postavsky <npostavs@gmail.com> wrote:
>
>> People might say things like "your height must be between 120 and 200 cm
>> to ride this roller coaster"
>
> This still puts "height" (the variable) first.
Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> And they don't say "120 cm must be less than your height, which must also
> be less than 200 cm". :-)
Right, but unless we want to use a macro like
IN_RANGE_P (height, 120, 200)
I think ((120 < height) && (height < 200)) is the closest we can get to
the natural phrasing. In Elisp we can do (< 120 height 200) which is
nicer, but we're still stuck with `and' for semi-closed intervals.
next prev parent reply other threads:[~2019-08-04 14:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 17:00 bug#19208: replace-match unhelpful error message Phillip Lord
2019-08-03 14:01 ` Lars Ingebrigtsen
2019-08-03 20:22 ` Paul Eggert
2019-08-03 20:31 ` Lars Ingebrigtsen
2019-08-03 20:50 ` Paul Eggert
2019-08-04 9:09 ` Andreas Schwab
2019-08-03 23:59 ` Noam Postavsky
2019-08-04 9:02 ` Andreas Schwab
2019-08-04 14:12 ` Noam Postavsky [this message]
2019-08-04 15:13 ` Andreas Schwab
2019-08-04 17:41 ` Paul Eggert
2019-08-04 18:14 ` Andreas Schwab
2019-08-05 2:25 ` Richard Stallman
2019-08-04 11:47 ` Lars Ingebrigtsen
2019-08-04 9:18 ` Andreas Schwab
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=87ef21rpe1.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=19208@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.org \
--cc=phillip.lord@newcastle.ac.uk \
--cc=schwab@linux-m68k.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 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.