Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100])
	by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with SMTP id q72NV3a6016311
	for <rainer@rainer-schoepf.de>; Fri, 3 Aug 2012 01:31:04 +0200
Received: (qmail 31821 invoked by alias); 2 Aug 2012 23:30:58 -0000
Delivered-To: GMX delivery to rainer.schoepf@gmx.net
Received: (qmail invoked by alias); 02 Aug 2012 23:30:58 -0000
Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212]
  by mx0.gmx.net (mx063) with SMTP; 03 Aug 2012 01:30:58 +0200
Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94])
	by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id q72NSXIt028355
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 3 Aug 2012 01:28:33 +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.1) with ESMTP id q72F1P39008220;
	Fri, 3 Aug 2012 01:28:33 +0200
Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with
          spool id 2447317 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 3 Aug
          2012 01:28:33 +0200
Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de
          [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.8/8.13.1) with
          ESMTP id q72NSXHI032353 for <LATEX-L@listserv.uni-heidelberg.de>;
          Fri, 3 Aug 2012 01:28:33 +0200
Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com
          [209.85.220.177]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with
          ESMTP id q72NSRn5016585 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128
          verify=FAIL) for <LATEX-L@listserv.uni-heidelberg.de>; Fri, 3 Aug
          2012 01:28:32 +0200
Received: by vcbfl13 with SMTP id fl13so118982vcb.22 for
          <LATEX-L@listserv.uni-heidelberg.de>; Thu, 02 Aug 2012 16:28:27 -0700
          (PDT)
MIME-Version: 1.0
Received: by 10.52.23.136 with SMTP id m8mr18777441vdf.28.1343950107496; Thu,
          02 Aug 2012 16:28:27 -0700 (PDT)
Received: by 10.220.149.2 with HTTP; Thu, 2 Aug 2012 16:28:27 -0700 (PDT)
References: <501AA3AA.5000400@gmail.com> <501AA936.9050205@morningstar2.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Whitelist: <blflatex@gmail.com>
Message-ID:  <CANQYN6zoBtCmA2QczWY6Y4+3AvKUQKaNRX0QWtdhKePpbVWKtQ@mail.gmail.com>
Date:         Fri, 3 Aug 2012 01:28:27 +0200
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: Bruno Le Floch <blflatex@GMAIL.COM>
Subject: Re: l3doc bug in syntax sections
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <501AA936.9050205@morningstar2.co.uk>
Precedence: list
List-Help: <http://listserv.uni-heidelberg.de/cgi-bin/wa?LIST=LATEX-L>,
           <mailto:LISTSERV@LISTSERV.UNI-HEIDELBERG.DE?body=INFO%20LATEX-L>
List-Unsubscribe: <mailto:LATEX-L-unsubscribe-request@LISTSERV.UNI-HEIDELBERG.DE>
List-Subscribe: <mailto:LATEX-L-subscribe-request@LISTSERV.UNI-HEIDELBERG.DE>
List-Owner: <mailto:LATEX-L-request@LISTSERV.UNI-HEIDELBERG.DE>
List-Archive: <http://listserv.uni-heidelberg.de/cgi-bin/wa?LIST=LATEX-L>
X-GMX-Antispam: 0 (BackTrace mail analyze);
 Detail=5D7Q89H36p4L00VTXC6D4q0N+AH0PUCnGL2vqOgpaBYL16oitsMrgDt/NQNpSCZFFjDOy
 97xb7Zpf+wZnd5ZXNcvLDXR3Wg3wRjdQbwEMh8=V1;
X-Resent-By: Forwarder <forwarder@gmx.net>
X-Resent-For: rainer.schoepf@gmx.net
X-Resent-To: rainer@rainer-schoepf.de
Status: R
X-Status: 
X-Keywords:                  
X-UID: 7095

On 8/2/12, Joseph Wright <joseph.wright@morningstar2.co.uk> wrote:
> On 02/08/2012 16:58, Joel C. Salomon wrote:
>>     "\some_function_with_a_very_long_name:nnnnn" <first argument>
>> <second argument> <third argument> <fourth argument> <fifth argument>
>
> Not related to the issue, but in general we've favoured
>
>   \cs{some_function} \Arg{with an argument}
>
> (Looking long-term, I think this might be better to avoid active
> characters, while \cs... offers more possibilities than just 'verbatim'
> when consdiering format conversions.)

I seem to recall using ^^A as a comment character in the syntax
environment (and really anywhere else in the "% ..." documentation
lines).

Regards,
Bruno