MIME-Version: 1.0
References: <CAM2dePV5k2+Q+H=jCj=bsvc-hWanc3_CLYw1-ukhB8UMhzU_Lw@mail.gmail.com> <51C94FA0.1080803@morningstar2.co.uk>
            <CAM2dePUfzF_Bj5QX7qbAmsyO7Udjy1yb5j43zTVexOwG2rmtVQ@mail.gmail.com> <51DD0EBD.6080308@morningstar2.co.uk>
            <CAM2dePUxFs1eNU1iTCrnp=CbDFo1eMjE813gZQH3vVhBkH=zDg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Message-ID:  <CAM2dePW_05F5MDijcp2Xp00Th2GcSa-GogUwHJ-pgm4ZLnNAbA@mail.gmail.com>
Date:         Wed, 10 Jul 2013 12:48:06 -0400
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: Jura Pintar <jura.pintar@GMAIL.COM>
Subject: Re: l3keys feature request
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <CAM2dePUxFs1eNU1iTCrnp=CbDFo1eMjE813gZQH3vVhBkH=zDg@mail.gmail.com>
Precedence: list
Content-Transfer-Encoding: quoted-printable
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

> By the way, the syntax and function of my initially proposed
> \keys_subgroups_set:nnn could be roughly captured by the following
> code (though I doubt it would add anything useful any more)

What I meant to say here is not that the new proposal does roughly
what \keys_subgroups_set:nnn actually did, but what I had wanted it to
do.

Come to think of it, though, it would perhaps be useful to have some
sort of ability to search across subgroups (independently of the
key-filtering application). Perhaps something corresponding to the
pgfkeys =92.search also=92 handler.