----- Original Message -----
> It's particularly difficult to understand what's going on with a given
> bug report when the log/manifest/terminal output is all being
> mis-interpreted as Markdown text.
>
> We'll definitely try and make this more obvious somewhere, but it
> really does help immensely if you use the <pre> and </pre> HTML tags
> in your bug reports to surround manifest excerpts, log output, and
> terminal commands.
>
> It helps a lot with long log lines, as we get them inside a scrollable
> container, and it clearly separates out the code/output from the
> language describing the issue.
it would help if redmine turned < into < etc in the pre blocks :)
>
>
> Example:
>
> Here's my test manifest, test.pp
>
> <pre>
> class hope {
> notice("I wish Puppet would do what I mean and not what I say")
> }
>
> include hope
> </pre>
>
> and here are the results when I apply it:
> <pre>
> kripke:~ nbk$ puppet apply -v /tmp/test.pp
> notice: Scope(Class[Hope]): I wish Puppet would do what I mean and not
> what I say
> info: Applying configuration version '1295819244'
> </pre>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Puppet Developers" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/puppet-dev?hl=en.
--
R.I.Pienaar
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
