Received: from mout-xforward.gmx.net (mout-xforward.gmx.net [82.165.159.14]) by h1439878.stratoserver.net (8.14.4/8.14.4/Debian-2ubuntu2.1) with ESMTP id s8TJnUa8020415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 29 Sep 2014 21:49:32 +0200 Received: from relay2.uni-heidelberg.de ([129.206.210.211]) by mx-ha.gmx.net (mxgmx008) with ESMTPS (Nemesis) id 0LtmCb-1YHP9N21GH-011EXa for ; Mon, 29 Sep 2014 21:49:25 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s8TJkF1u028954 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Sep 2014 21:46:15 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s8TE3E6Y025610; Mon, 29 Sep 2014 21:46:15 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 11302732 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 29 Sep 2014 21:46:15 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s8TJkEEi012725 for ; Mon, 29 Sep 2014 21:46:14 +0200 Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id s8TJk71l004130 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for ; Mon, 29 Sep 2014 21:46:09 +0200 Received: by mail-wi0-f174.google.com with SMTP id cc10so852368wib.13 for ; Mon, 29 Sep 2014 12:46:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=J9ZOETM6PpYueecHcagA7bP3RUil6RkdGyiwfAF5WWg=; b=G9lEliIB1NqdH+EVGL7trS6u3TfCns49Q+oRDVPBEf8lUPdT3Tt5AqliRYlIaZdw73 BmBafbFBZRUZmOtozrys8AN/0D91rsuGnOgCiiQah61YkaGxFU5npBkKte7p488nSBxq MRudg2svGqxd78lyBtyOU8xAkDagKra2rdbEfNVz9jGkItQ5gLceBGeq44uqb+DX5wNf Apv75TSuqUTYJLCL/fp2bXhhm6FUupp+KC4dM6AF1F2ftl8aWVWa5i/eQErgJSrGOlqd tln/PRIOVxTESC0jKsJCETyAlQDGVsdvvPY5D+FIgV8EGdHsLtFK50rv4BX6pQ0Rn9mp rqGQ== X-Gm-Message-State: ALoCoQk7WuE+Q5Oejm/3ErSuS02c/mev6uxtuMfEtFqiTDXPbdxaMTC3uQNf8DJCUQPZoTTKIjbF X-Received: by 10.194.20.230 with SMTP id q6mr46812330wje.53.1412019966925; Mon, 29 Sep 2014 12:46:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.27.49.72 with HTTP; Mon, 29 Sep 2014 12:45:46 -0700 (PDT) References: Content-Type: multipart/alternative; boundary=047d7b5d971b8b90a8050439842c Message-ID: Date: Mon, 29 Sep 2014 15:45:46 -0400 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: "Allred, Sean" Subject: Re: [l3keys] Suggestion: Add a key property for specifying key that /has/ to be used To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: Envelope-To: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=V3; X-GMX-Antivirus: 0 (no virus found) X-UI-Filterresults: notjunk:1;V01:K0:hzSCJh9D96Q=:LWKTrNB+JPpKXmFJZbBmxMOhOd 8LcAj24Lo3Kb2PpBXGMQaBLve+VwFZo/WCG8xJBSqnNIlEZrep312A2PFWc1/oA+92DtzmBFD pVvCCxK4s3OK5Q0bNBOt6su9M+D3uu0J5mGrLXclXNWmI1A43NF8o2zCuRCLLh+f6lM933R3T EUdYvrF4bclD7uS/uiJS33cuoADa4xvc/Mdk9Hf9OkVWtEWN5+I2M/Uz8mehuTs37XyDEEWHS +TXTvtAwNbmsBBqhYTPsUcz6+Q5aTb2dNh2piZ2KqEiQLal3LzTSlYxaVIpiXCSfkGdz8jgCS Ll5Ou/8cqWOde4O1h9vfVgMl8k4cxrn6kkpfEjhArbIwYpfCMtQzYWaH0ak5JgKN5RjCCPC4m dY6p8bUFxqbI68KVeKNb0x8sSvBhqjck7+yZ7dnE9X3pWPDuGzkaaOtTMhguHzXyH5+cF2B4d Ldn4dDPewRwGkpLH9IA/EF87vXpR02D3YVpf1l572sxPq026RjIabBsk9F/gYkjSGmgCVxhdU Y4YKojvFbPrKdg2GQPfU+ZTsm0FkiqkpmTuuuLY8biqbEFIhFx1//kYYyuSLb/19+fetYbYLj XDUB+T9FmKyLlJsU+6JNG5i2i0qT4MajuAFT17eIocIvezcam11cfUpWOR1A8m/nTa4jmBVMd HRwqJJeTdJxNxt/JTCEjKnLQOICGEUhlINyT/mfIG7pcevtfBqNHuTO9zgcN4XBiv584Wb96i CkCo2zYjDYw64sCkirlpwT6GttWJaik7vI7GxjsUErQgjCA2Xg/YlqFBfrxb6AmIRT23OiZKl Fq3mnTxe1XdZMmU08KorX1sFq/rmJq9Rdcz26Jhs/Q/7qqem6GOUa2rFefzI1hvea15e4BFtd 4mVO18ONxcb3LrLdPIe/9wKdJ27XQ0yugkLD8SF33QJ7jdYVsO1V5cvUpIdtoGePthjISvk+X /D5RAy5kBPZ9hvjNbO/5dRLNv61ZXXjETHSKu8agX3bTJ4L3U6UFj5NMFqPW+gaGaRDmk/o47 j0bLLYOMSQGztuD4blGQ8nT2xuijzvy97ZfuAUPxm+x+z29bgV5Nq/eldp9m3jJggbZDLN9sZ tG1xyG6i/dCpxZRGc/SvBJHuWVp9WITZ5WVC5m89ZJz3F0tlZ2UlxYa52WwSABPRiqnpihrXX iIT5lUm4lKPIrbxDNNShrJnPvzCNg/1QS1+sONeVE5Q6D+RhxGcE8hf6eObkCyICslv5mbbB0 xJF8nIgMMOU8VQ0x1MOev1lFZGTtrOUs/Y+BFDK4CC1cB2a6NuVm7NF+4RFt22xlCILao5Pxi /30WBx8mTwtnBvSQRorwKnGhA1wK6Z83rFrKVG9mQ0ObT8tH8IRqo2dGpdYSxTnza37dREj82 XccVOjP5CMMyrZfpCbj7pWB6G5uVWs/vDNQ8vKP/IFGzAkiU3nOjvgLE0PsPvpnpCjL1ZEM3R 8j6IIkdEPlcTNhMhhLyTNsR/v3KEfF98CRO4wY9psNYU9MW531 X-UI-Loop:V01:rYEjdeKbbE4=:ZobFA3VmVEs6Ydb+mo5qZ2AaGEXZQHsWuZbzxNvM3/A= X-UI-Out-Filterresults: junk:10; X-Scanned-By: MIMEDefang 2.71 on 85.214.41.38 Status: R X-Status: X-Keywords: X-UID: 7601 --047d7b5d971b8b90a8050439842c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'll just chime in and say that this topic is *awfully* similar to http://thread.gmane.org/gmane.comp.tex.latex.latex3/3363. On Mon, Sep 29, 2014 at 5:37 AM, Denis Bitouz=C3=A9 < denis.bitouze@lmpa.univ-littoral.fr> wrote: > Hi, > > among others, `.value_forbidden:` and `.value_required:` key properties > from `l3keys` package are useful: they let us specify that a given key, > when used, either cannot or must receive a value. > > What could be useful as well is a key property, say `.required:`, that > would > specify that the corresponding key /has/ to be used. This could be helpfu= l > for > instance in the case of a document command `\MyModuleSetup` for setting u= p > a module `mymodule`: > > \DeclareDocumentCommand \MyModuleSetup { m } > { \keys_set:nn { mymodule } { #1 } } > > where some module property /has/ to be specified. > > I know this can be achieved with something like test of existence of > some tokenlist and message emitted in case of nonexistence but a high > level key property for this could be nice. > > May I ask what is your opinion about that? > > Thanks in anticipation. > -- > Denis > --=20 Sean Allred --047d7b5d971b8b90a8050439842c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'll just chime in and say that this topic is *awfully= * similar to=C2=A0http://thread.gmane.org/gmane.comp.tex.latex.latex3/3363.= =C2=A0

On Mo= n, Sep 29, 2014 at 5:37 AM, Denis Bitouz=C3=A9 <denis.bi= touze@lmpa.univ-littoral.fr> wrote:
Hi,

among others, `.value_forbidden:` and `.value_required:` key properties
from `l3keys` package are useful: they let us specify that a given key,
when used, either cannot or must receive a value.

What could be useful as well is a key property, say `.required:`, that woul= d
specify that the corresponding key /has/ to be used. This could be helpful = for
instance in the case of a document command `\MyModuleSetup` for setting up<= br> a module `mymodule`:

=C2=A0 =C2=A0 \DeclareDocumentCommand \MyModuleSetup { m }
=C2=A0 =C2=A0 =C2=A0 { \keys_set:nn { mymodule } { #1 } }

where some module property /has/ to be specified.

I know this can be achieved with something like test of existence of
some tokenlist and message emitted in case of nonexistence but a high
level key property for this could be nice.

May I ask what is your opinion about that?

Thanks in anticipation.
--
Denis



--
Sean Allred
--047d7b5d971b8b90a8050439842c--