From: Drew Adams <drew.adams@oracle.com>
To: "Po Lu" <luangruo@yahoo.com>, "Mattias Engdegård" <mattiase@acm.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: master 6eeab90632: Don't accept whitespace or hex floats in rgbi: colour specs
Date: Mon, 7 Mar 2022 16:06:05 +0000 [thread overview]
Message-ID: <SJ0PR10MB548884A6F0729357963F6F56F3089@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87zgm2m5lv.fsf@yahoo.com>
> If the happenstance doesn't cause trouble, there is no need to get rid
> of it.
As I suggested, mentioning other, similar contexts:
But if you want/need to know _whether_ some
data is well-formed ______ according to the
standard, then you don't want to allow data
that's not well-formed.
Whether or not you want to support such a use case,
i.e., _checking_ whether something is ONLY an rgbi
code and not something that also includes whitespace,
is up to you. But it's easy to provide users with
both behaviors, by adding an optional arg (LAX or
STRICT), depending on what you want the default
behavior to be.
prev parent reply other threads:[~2022-03-07 16:06 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
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 ` Drew Adams [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=SJ0PR10MB548884A6F0729357963F6F56F3089@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--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).