MIME-version: 1.0
Content-type: text/plain; charset=utf-8; format=flowed
Content-transfer-encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
            Thunderbird/38.7.2
Message-ID:  <58840912.7090202@clear.net.nz>
Date:         Sun, 22 Jan 2017 14:21:22 +1300
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: Andrew Parsloe <aparsloe@CLEAR.NET.NZ>
Subject: l3keys2e documentation
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

I am confused by the illustration

\keys_define:nn { module }
   { option .set:N = \l_module_variable_tl }

in the l3keys2e documentation. I thought, "Ah, this is how you 
distinguish package options from keys defined within a package", but 
when I try this it doesn't work. But

\keys_define:nn { module }
   { option .tl_set:N = \l_module_variable_tl }

does.

Andrew

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus