Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
References: <C58398B6-8915-458C-AF38-F3C82F9342B2@gmail.com>                   
            <4E4FF538.7070601@morningstar2.co.uk>
            <9788A2B7-3E8F-4D2C-A52E-10999BCB59FA@gmail.com>
            <4E516DF2.4040002@morningstar2.co.uk>
            <104nbkj0nr84x.dlg@nililand.de>
            <4E523217.2080408@morningstar2.co.uk>
            <cybpko27uiip.dlg@nililand.de>
            <4E52AA87.6090608@morningstar2.co.uk>
            <1i25hv8yiyx81$.dlg@nililand.de>
Content-Transfer-Encoding: 8bit
Message-ID:  <0724DD9F-916F-475B-8A67-FCBB6297F670@gmail.com>
Date:         Tue, 23 Aug 2011 18:15:55 +0930
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
Sender: Mailing list for the LaTeX3 project <LATEX-L@listserv.uni-heidelberg.de>
From: Will Robertson <wspr81@GMAIL.COM>
Subject: Re: couple of l3keys notes
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <1i25hv8yiyx81$.dlg@nililand.de>
Precedence: list
Status: R

On 23/08/2011, at 6:02 PM, Ulrike Fischer wrote:

> Am Mon, 22 Aug 2011 20:14:15 +0100 schrieb Joseph Wright:
> 
>> I have added the scheme broadly as outlined above to l3keys. Feedback
>> would be welcome. For example, does 'set_known' convey the appropriate
>> idea? 
> 
> I don't have enough practice with l3keys to decide this - just
> starting. But from the language I would expect a \keys_set_known to
> give an error if it encounters something unknown. Also a command to
> set keys can set only known keys, so it sound like a pleonasm. 
> 
> Perhaps \keys_set_store or \keys_set_keep would be better?

I must confess I prefer \keys_set_known, which I associate with "set keys *which are known* of #2".

I guess this is a bad time to mention that I just realised that \keys_set:nn is a weird name in the first place, since it's actually more general that assigning values to variables. (In fact, I often write \keys_set when I mean to write \keys_define.) But I think it's okay and I can certainly live with it; I'm not proposing a change of name to \keys_process:nn !

-- Will