Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
References: <501AA3AA.5000400@gmail.com> <501AA936.9050205@morningstar2.co.uk>
            <CANQYN6zoBtCmA2QczWY6Y4+3AvKUQKaNRX0QWtdhKePpbVWKtQ@mail.gmail.com>
            <CAFUtaNH9ObvaskLSgvxhGS8we2NjwzE2h2dirJHBzAtSML51VQ@mail.gmail.com>
            <CANQYN6w8Qs=qd6ey6+0wv0q6LN8K4QRByTvn62d8EyZ8OpPOZQ@mail.gmail.com>
Content-Transfer-Encoding: 8bit
Message-ID:  <4453C269-8281-443D-A548-C9B49B4E37B4@gmail.com>
Date:         Sun, 5 Aug 2012 13:46:31 +0930
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: Will Robertson <wspr81@GMAIL.COM>
Subject: Re: l3doc bug in syntax sections
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <CANQYN6w8Qs=qd6ey6+0wv0q6LN8K4QRByTvn62d8EyZ8OpPOZQ@mail.gmail.com>
Precedence: list
Status: R

On 03/08/2012, at 9:53 PM, Bruno Le Floch wrote:

> Admittedly, none of the three "solutions" is great.  As Joseph notes,
> we've gone for a single line in the l3 source.  We could perhaps add
> \def\^^M{\unskip\space\ignorespaces} to the \begin{syntax} setup: this
> would allow
> 
>    \cs{some_function_with_a_very_long_name:nnnnn} \
>      \Arg{first argument} \Arg{second argument} \
>      \Arg{third argument} \Arg{fourth argument} \
>      \Arg{fifth argument}

I've been thinking for a while that having \obeylines in the syntax environment (which predates my involvement on this code IIRC) has made certain things rather awkward.

It would be an annoying change to have to implement in our sources, but what do you think about dropping \obeylines?

-- Will