all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 19208@debbugs.gnu.org, Phillip Lord <phillip.lord@newcastle.ac.uk>
Subject: bug#19208: replace-match unhelpful error message
Date: Sat, 3 Aug 2019 13:50:55 -0700	[thread overview]
Message-ID: <f4ff92f3-8d0c-1abc-e986-2f04aae352b9@cs.ucla.edu> (raw)
In-Reply-To: <87imrec7oq.fsf@mouse.gnus.org>

Lars Ingebrigtsen wrote:
> they are
> demonstrably confusing for people not used to seeing conditionals
> written that way, which is I think pretty much everybody, except four
> people working on Emacs.  :-)

Just four?  :-)  (Actually the style is also used in other GNU projects.)

In this particular case the Leibniz style caught a potentially-serious bug. 
Although I understand that it can be a minor irritation for newcomers, it is 
quite useful for range checking and in practice I find that its reliability 
outweighs any irritation. (I didn't like Val Schorre's advice either, when I 
first heard it - but he was right.)





  reply	other threads:[~2019-08-03 20:50 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 [this message]
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
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=f4ff92f3-8d0c-1abc-e986-2f04aae352b9@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=19208@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=phillip.lord@newcastle.ac.uk \
    /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.