Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by h1439878.stratoserver.net (8.14.4/8.14.4/Debian-2ubuntu2.1) with ESMTP id t7P9RMMs008237 for ; Tue, 25 Aug 2015 11:27:23 +0200 Received: from relay2.uni-heidelberg.de ([129.206.210.211]) by mx-ha.gmx.net (mxgmx009) with ESMTPS (Nemesis) id 0MdWLU-1Z4vSC28Q0-00POJx for ; Tue, 25 Aug 2015 11:27:16 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id t7P9OOiE004057 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Aug 2015 11:24:24 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id t7P9H5wg015547; Tue, 25 Aug 2015 11:24:24 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 12531878 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 25 Aug 2015 11:22:17 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id t7P9M9vA001153 for ; Tue, 25 Aug 2015 11:22:16 +0200 Received: from nov-007-i507.relay.mailchannels.net (nov-007-i507.relay.mailchannels.net [46.232.183.61]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id t7P8YmlV030380 for ; Tue, 25 Aug 2015 10:34:53 +0200 X-Sender-Id: netnames|x-authuser|joseph.wright@morningstar2.co.uk Received: from smtp3.easily.co.uk (ip-10-229-11-165.us-west-2.compute.internal [10.229.11.165]) by relay.mailchannels.net (Postfix) with ESMTPA id 4C5E1120902 for ; Tue, 25 Aug 2015 08:34:42 +0000 (UTC) X-Sender-Id: netnames|x-authuser|joseph.wright@morningstar2.co.uk Received: from smtp3.easily.co.uk (smtp3.easily.co.uk [10.21.145.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.5.1); Tue, 25 Aug 2015 08:34:43 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: netnames|x-authuser|joseph.wright@morningstar2.co.uk X-MailChannels-Auth-Id: netnames X-MC-Loop-Signature: 1440491682716:3160180792 X-MC-Ingress-Time: 1440491682716 Received: from [139.222.114.163] (port=51933 helo=[139.222.114.163]) by smtp3.easily.co.uk with esmtpa (Exim 4.43) id 1ZU9gl-00043x-RI for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 25 Aug 2015 09:34:39 +0100 References: <55DBB7F6.1070307@clear.net.nz> <55DABA1D.3050706@morningstar2.co.uk> <55DCFDF7.7080305@clear.net.nz> <9F80F164-248C-4E5D-B799-B42DE56A6016@gmail.com> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-AuthUser: joseph.wright@morningstar2.co.uk Message-ID: <55DC289F.90001@morningstar2.co.uk> Date: Tue, 25 Aug 2015 09:34:39 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: Catcode changes To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <9F80F164-248C-4E5D-B799-B42DE56A6016@gmail.com> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: Envelope-To: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=V3; X-GMX-Antivirus: 0 (no virus found) X-UI-Filterresults: notjunk:1;V01:K0:pLrZbDWNAwo=:LCZ5sqytkoDqcD3wYG0dZa8KOM ScOwDQhAy3MXAF4yipF4Zw4Rh3LMoMd+pQ7+5j5vzQqeJ5I9SJj7m8OIvePAQVHmk2qrv6dq/ vSKWgURHYE2dzA8LjAFEZcGc9FTP8gXNCkdHL9H4P9qfO5P/003nP4stMNwwyW8YGx1bW8wPm Mg8ZwlrBMOgK0ax3RhpHSc9AvSzUUHC0opgO9wjwRlwrEAc8XIZF1Ov34s76vXiEiY4E1y07J N2s5LMC1lNldzBq6jn8sKNnXAl580/CsmAJpj19TtVY+Vv6YXi/5hMSn+Oq6FBprsfkUdaTwC IQ7N532JXBJ9sR2v+vyswMiXVFaHCGMHWsGlPpNBGPqUGldTFENALCPOTRLomVz6rJPmkZx3X g7FYUYN5XTivCOSlt10Gjqq8OjjNWXDQewMTgmFfMwPdVNmh+FjUzsmUQXx/5xb9sim/Mn9cY vJVeu5U0issXNOkztl/4rcEP6cSBsLcp+og3MRUQgffQEeLhvWyPPa8cSiBwAIE4OG21KC//H /P+PXGM7p1tey8oTo+c5Hf7bCV8LgTcS2svSNmM/2aqb7kMgpVnfq/NIcwx29pj/JtcY1Du+M CVmrKyuAhec8M374DAqa4nL7SnS6FAG1KyC2i5T8mI5FpY2XwhaC1z7FdC6dzfP1gpVzQjUtX P/QTWnD0Sd+ejaLs0NSge6xpZAcZhljQAkxibB5dyOQO/V/exOAqQahI/W4SrSOa7Eso95P0G usPDRAn49DFfyazToA3Ld4tch4fPdnJbf13vevJS8a0iY5kIV7zjUhyNYgdD490vrCWOSY46z cauxYAN0tndurYDEx9jMY93bx7kp0bCKhF+FYo1iBgohtz3xB7j+yEDCgOfuylj2+GcLaaAtB yGcAkTPtjwzhUt9uQv94runt49rW1xyDZEPn2doZLrP9rlJXVJipWcdrY7T6CNwu0tKrOGSeU +pcVPh4n0D022s79lZk9cIEhlr9+81JQJK970dMMQGmWbDIQUbn/6i43YXlDUizIoW+uKrVy0 SNQxfZOLFzL5RK7yhccAdmS4sB5UFMe9IZlhSQ6NA3eZc0/xRQ6eEgLksuUZWsrAJb6Sf+ayW SZwEg7s21huUolSxDtfuPofuQbYkHB4CE+n5E1ckOVnsi3LQs+blL6BO7HfU5GUXWimhEcT/h cPqB73v1MFb52F9ftalUZF2zpoeMA9257eksAv35b0oG+ZaCr3fOvNDJhGqcb7Uy7woLUr/gQ EJWU+wFosw9SQD0AyViPOiLcWpqLS0Qh5yZJ3K7UIe3hQHtXWWvfqsZniGk9j3ByGzBP39SXf rAhFoOFbjvtwXaVUpliKdv4XECgLXktCfCgRfE3dUBBFKASyijrU/8UdO2iZigCzhQ43tmn+n z+U+AtEbI/x684BJ/WFy2D/0bxLKJxfvzR7OS7s+sK4I8NwaLMsJAJGF86oWn0W8mlKF4V6KW Srou7TWzX45p7bMuwhqYAr2dw8ufZrwhqFkDKt0U8x2WuUa6uoz1/pP5kCjdMUGCR4tJ2QlA= = X-UI-Loop:V01:mfYN/KbD6nc=:7zb3VoSaacJQGvQk+z1qXn/Ftc0yApejehy4vk5uxoQ= X-UI-Out-Filterresults: notjunk:1;V01:K0:doFzFiean90=:caSJW/3A1ocRFZSgKgvvUJ J/Sn8n9kEth7gmrKLOMRy4jsb0mUaEA7+TFosHnb0HFZup1hSUaLu9A1zFSzXxDx3C1JY1rJ5 oLWu8lKcJcK97MqVjvfXN9zN8mFeJKobQo/VK04CbqHKbSXAaxgVtRRHoPjB23jj4YGWGdSNg TDr5rc670s/T5fqGHFoohyH+busqMsLQ+H6y4IkR8YXchl/K/+tLMska9P99e4bnnTA/NF0+n hmuM6lxnJSD6togyGbJ2fz7wAncDLq8JpaxZzCoghfEjnj0oUAsxh42vba2VWCP0r+6eiZK4t 5GPeBN4JFVPUA3C6YxkJJZ+wwHkAffGVTJueaWK3oge15vzmj6pgv1kp3OunrujLo6BeHgGgk +8XLBnB5T/ClQg8TPO7VnrrBb2xm06YzukWEsls2mUibPVTFvYVwNr7vBgdOBorxTPnbLF8dk YQ1z083pJpt413d9XvGwMFSK8hdWtXDyqpsRGuPCUA3ERYvJdsl3 X-Scanned-By: MIMEDefang 2.71 on 85.214.41.38 Status: R X-Status: X-Keywords: X-UID: 7833 On 25/08/2015 06:16, Will Robertson wrote: > On 26 Aug 2015, at 09:14, aparsloe wrote: >> >> (1) I wanted to use \tl_replace_all:Nnn on a token list that might contain braced groups. > > We might want to consider a "nesting" map function that essentially disregards brace groups. This could be used to define a new \tl_replace_nested:Nnn or similar for exactly this purpose. > > I'm fairly sure Bruno already has code that does nested mapping as part of his "tl" extensions... What do others think? I guess I'd want to know a bit more about use cases. As I've said on LaTeX-L, normally brace groups are an 'escape' mechanism from the scanner, so I'm not sure I'd expect recursive replacement as a general thing. I'm wondering if this is being used for something rather 'text like', which might be handled by l3regex (slow but for a smaller number of cases reasonable). Joseph