User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
References: <48CC30E3.9020308@morningstar2.co.uk>                      
            <48CD7104.4000103@residenset.net>                      
            <48CDFCBB.8050509@morningstar2.co.uk>           
            <5F3DB0EC-4917-4354-8D90-2237C6D4F685@gmail.com>           
            <48CE55F1.9030804@morningstar2.co.uk>
            <A519E427-60D4-4EAF-A76C-BC7512DBCDE4@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID:  <48CE64D2.8070601@morningstar2.co.uk>
Date:         Mon, 15 Sep 2008 14:36:18 +0100
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: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: Suggestions sought
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <A519E427-60D4-4EAF-A76C-BC7512DBCDE4@gmail.com>
Precedence: list
Status: R

Will Robertson wrote:
> On 15/09/2008, at 10:02 PM, Joseph Wright wrote:
> 
>> That is a somewhat different issue, I think. As I said, the problem here
>> is my lack of knowledge of how to get the "hooks" to reproduce exactly
>> the input, including the "#1", etc., signs.
> 
> Oh, sorry -- I misinterpreted what you were doing as being rather
> similar to patchcmd itself.

I'm essentially trying to get the pgfkeys handler ".add code" to work
correctly with ".ecode args".  You'll see on c.t.t that I've pointed out
that the pgfkeys methods goes wrong when this is tried.  As I don't
currently have a solution, I'm going with a controlled error.
-- 
Joseph Wright