LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Mon, 15 Sep 2008 13:32:49 +0100
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=ISO-8859-1
From: Joseph Wright <[log in to unmask]>
Parts/Attachments: text/plain (28 lines)
Will Robertson wrote:
> On 15/09/2008, at 3:42 PM, Joseph Wright wrote:
>> So my attempts to create a simple hook:
>> \def:cpx {<key>} <arg spec.> {\exp_not:N\prehook <code>
>> \exp_not:posthook}
>> fail when the added code contains #1, #2, ... My current approach at
>> least does not give a TeX error under these circumstances (I've added a
>> custom one to warn of a problem).
>> I'm sure I'm mossing something, but my knowledge of TeX's approach to
>> doubling # characters, etc., is clearly insufficient to find it.
> Maybe as a pre-cursor to this work we should port patchcmd to expl3?
> Even that package only handles "plain" argument specs, though.
> W

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.

Of course, \patchcmd would be nice for other things (as I've already said).
Joseph Wright