Re: [Docutils-users] including source code

[Alan G I. <ai...@am...>]

> On Tue, 10 Oct 2006, Alan G Isaac wrote:=20
>> I suggest that the LaTeX writer handling of literal=20
>> inclusions needs to be rethought.  Right now I think the=20
>> right approach is to add an option:=20
>> --literal-block-environment=3D[verbatim|verbatimtab|lstlisting|verbatimi=
nput|verbatimtabinput|lstinputlisting]=20
>> Those 6 cover most needs, and the list could easily be=20
>> expanded in the future if needed.=20

On Wed, 11 Oct 2006, (CEST) gr...@us... apparently wrote:=
=20
> why ? what does not work ? not that there are no bugs, there are for=20
> sure, but a solution without a problem is hard to test if it works.=20

> literal blocks might be real or parsed literal blocks. the=20
> later are "parsed" which means they might contain bold or=20
> emphasize markup.=20

> that is the reason why the option got the "-if-possible" tail, in some=20
> cases it isnt possible.=20

> so literal actially is two. using the stylesheet might go along=20
> making two newenvironments docutilsliteral, for things without markup and=
=20
> docutilsparsedliteral for things with markup.=20


Yes.  I am not speaking of parsed literal blocks.
Only real literal blocks.

I would personally be satisfied if I could just put these in
a listings environment (rather than verbatim).  But I was
trying to think of what others might want, and your use of
the verbatim environment suggests others might want=20
verbatim.

Let's take this in two pieces: minimal change to fix the=20
current problem, and then a more forward looking approach.

The minimal change to fix the current problem:
use the verbatimtab environment, which treats tabs appropriately.
The verbatim environment ignores tabs and in that sense is=20
not "literal".  I suggest setting the tabs to 4 spaces
(the default is 8).

Looking forward:
there can be good reasons for each of the other options=20
I listed.  **Especially** lstlisting, since literal blocks=20
will often be code.  (The listings package is awesome!)
Why rule them out?  If we agree that we are only talking=20
about real literal blocks here, it is really just a matter=20
of a usepackage declaration (moreverb or listins) and the=20
right environment (user specified).

Thanks for considering this.

Cheers,
Alan