unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 6eeab90632: Don't accept whitespace or hex floats in rgbi: colour specs
Date: Mon, 07 Mar 2022 08:34:51 +0800	[thread overview]
Message-ID: <87wnh6ob10.fsf@yahoo.com> (raw)
In-Reply-To: <77E09460-1313-41CC-B52A-B586A1D2671F@acm.org> ("Mattias Engdegård"'s message of "Sun, 6 Mar 2022 14:56:50 +0100")

Mattias Engdegård <mattiase@acm.org> writes:

> It's bug#54263 -- sorry about the omission from the log message.

Thanks.

> So it might seem, but over-tolerant implementation is generally a
> mistake. It restricts compatibility in the other direction (what
> worked with Emacs won't work elsewhere)

AFAICT, there are no other implementations of such an rgbi color
specification (please correct me if I'm wrong.)

> restricts future changes and implementations, detects fewer user
> mistakes, and makes documentation and specifications less useful. It's
> not doing the user a service.

I don't think there's a chance that the user will type any of those by
mistake.  Besides, the documentation can always be amended, and that
function has no other specification.  So I disagree that it doesn't do
the user a service.



  parent reply	other threads:[~2022-03-07  0:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164657208058.1597.5057681041192670917@vcs2.savannah.gnu.org>
     [not found] ` <20220306130800.EE0F9C01681@vcs2.savannah.gnu.org>
2022-03-06 13:46   ` master 6eeab90632: Don't accept whitespace or hex floats in rgbi: colour specs Po Lu
2022-03-06 13:56     ` Mattias Engdegård
2022-03-06 16:49       ` [External] : " Drew Adams
2022-03-07  0:34       ` Po Lu [this message]
2022-03-07  9:26         ` Philip Kaludercic
2022-03-07 10:16           ` Po Lu
2022-03-07 15:16             ` Philip Kaludercic
2022-03-07  9:31         ` Mattias Engdegård
2022-03-07 10:14           ` Po Lu
2022-03-07 13:36             ` Mattias Engdegård
2022-03-07 13:52               ` Po Lu
2022-03-07 16:06             ` [External] : " Drew Adams

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=87wnh6ob10.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=mattiase@acm.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).