On Thursday, 13 Oct 2016 at 12:46, Peter Davis wrote:
>> For completeness, would you please tell us your solution? I'm sure this
>> question will come up again at some point...
>>
>
> Sure thing, Eric. Basically, I just added the following to my org file:
Thanks. Useful to have the definition f
On Thursday, 13 Oct 2016 at 12:46, Peter Davis wrote:
> NOTE: The prebreak and postbreak definitions just add little red hooks
> to the source block to show me where a line break was added. It's a
> trick I picked up on this list a while ago.
Oh, and thanks for this! This is very useful.
--
: E
On Thu, Oct 13, 2016, at 04:08 AM, Eric S Fraga wrote:
> On Wednesday, 12 Oct 2016 at 16:35, Peter Davis wrote:
>
> [...]
>
> > Excellent! Thanks to this, I now have great looking JavaScript
> > listings, and I can easily change the styling.
>
> For completeness, would you please tell us your
On Wednesday, 12 Oct 2016 at 16:35, Peter Davis wrote:
[...]
> Excellent! Thanks to this, I now have great looking JavaScript
> listings, and I can easily change the styling.
For completeness, would you please tell us your solution? I'm sure this
question will come up again at some point...
T
On Wed, Oct 12, 2016, at 11:39 AM, Nick Dokos wrote:
> Peter Davis writes:
>
> > A. Source code listings
> >
> > 1) Source code blocks: Using
> >
> > #+BEGIN_SRC js
> >
> > works for HTML output, but not for LaTeX/PDF. It seems js is not
> > understood by the listings package, and I have to use
Peter Davis writes:
> A. Source code listings
>
> 1) Source code blocks: Using
>
> #+BEGIN_SRC js
>
> works for HTML output, but not for LaTeX/PDF. It seems js is not
> understood by the listings package, and I have to use java.
>
> 2) Even with java, the output is pretty ugly. Any way to get som
