LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Ulrike Fischer <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Tue, 23 Aug 2011 10:32:27 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
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?


> Show the variable used for storing the 'return' value be fixes, or
> flexible as in
> 
>   \keys_set_known:nnN { <module> } { <keys> } <return-var>

I would prefer a flexible variable. I remember that the fixed XKV@rm
from xkeyval had a tendency to get lost when keys itself called
setkeys. 


Another question: pdfkeys has the notion of a "key tree" and
"pathes". And you can switch pathes with a command. (.cd I think).
Can/should one do something similar with l3keys? I see the
subgroups, but I'm not sure if they really are the same conzept.


-- 
Ulrike Fischer 

ATOM RSS1 RSS2