Default syntax for code blocks?

Default syntax for code blocks?

[Nick Moffitt]

Is there an easy way to specify that all code blocks (fenced, `inline`, etc) are treated by the same syntax highlighter?

I am working on a document that has a lot of Scheme code, and it's rather infuriating to have to do things like `12`{.scheme} to get numbers formatted in paragraphs the way they are in the larger fenced code blocks.  I find myself taking shortcuts like `myfuncname` to save typing, but have to track down evry `else`{.scheme} so things are consistent.  I'm finding myself going mad when examples like `(this and that atom)` don't render the same as `(this and that atom)`{.scheme} because `and` is a reserved word.

I'd find my document much easier to work on if I could just say "everyting in backticks is scheme.  Format it."

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/20201121173412.GP4166%40zork.net.

Re: Default syntax for code blocks?

[John MacFarlane]

There is an option to set the default syntax for indented
code blocks. So, you could just use indented blocks.

To add a default class to all code blocks that lack one,
you could use a simple lua filter.

Nick Moffitt <nick-iTLVOByc1N8@public.gmane.org> writes:

> Is there an easy way to specify that all code blocks (fenced, `inline`, etc) are treated by the same syntax highlighter?
>
> I am working on a document that has a lot of Scheme code, and it's rather infuriating to have to do things like `12`{.scheme} to get numbers formatted in paragraphs the way they are in the larger fenced code blocks.  I find myself taking shortcuts like `myfuncname` to save typing, but have to track down evry `else`{.scheme} so things are consistent.  I'm finding myself going mad when examples like `(this and that atom)` don't render the same as `(this and that atom)`{.scheme} because `and` is a reserved word.
>
> I'd find my document much easier to work on if I could just say "everyting in backticks is scheme.  Format it."
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/20201121173412.GP4166%40zork.net.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/m28saufmps.fsf%40MacBook-Pro.hsd1.ca.comcast.net.

Re: Default syntax for code blocks?

[Nick Moffitt]

I can't use indented code blocks inside of paragraphs, headings, and definition lists, surely?

What would such a lua filter look like?  Is there any example out there that makes it clear how to do such a thing?

On 21Nov2020 01:01pm (-0800), John MacFarlane wrote:
> 
> There is an option to set the default syntax for indented
> code blocks. So, you could just use indented blocks.
> 
> To add a default class to all code blocks that lack one,
> you could use a simple lua filter.
> 
> Nick Moffitt <nick-iTLVOByc1N8@public.gmane.org> writes:
> 
> > Is there an easy way to specify that all code blocks (fenced, `inline`, etc) are treated by the same syntax highlighter?
> >
> > I am working on a document that has a lot of Scheme code, and it's rather infuriating to have to do things like `12`{.scheme} to get numbers formatted in paragraphs the way they are in the larger fenced code blocks.  I find myself taking shortcuts like `myfuncname` to save typing, but have to track down evry `else`{.scheme} so things are consistent.  I'm finding myself going mad when examples like `(this and that atom)` don't render the same as `(this and that atom)`{.scheme} because `and` is a reserved word.
> >
> > I'd find my document much easier to work on if I could just say "everyting in backticks is scheme.  Format it."
> >
> > -- 
> > You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/20201121173412.GP4166%40zork.net.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/20201121210354.GQ4166%40zork.net.

Re: Default syntax for code blocks?

[Nick Moffitt]

I was sceptical, as while I love lua, the AST API has always baffled me in pandoc. But it really was simple in the end!

```{.lua}
function Code (el)                                                              
	table.insert(el.classes, "scheme")                                                                  
	return el                                                                     
end                                                                                
function CodeBlock (el)                                                         
	table.insert(el.classes, "scheme")                                            
	return el                                                                     
end
```


On 21Nov2020 09:03pm (+0000), Nick Moffitt wrote:
> I can't use indented code blocks inside of paragraphs, headings, and definition lists, surely?
> 
> What would such a lua filter look like?  Is there any example out there that makes it clear how to do such a thing?
> 
> On 21Nov2020 01:01pm (-0800), John MacFarlane wrote:
> > 
> > There is an option to set the default syntax for indented
> > code blocks. So, you could just use indented blocks.
> > 
> > To add a default class to all code blocks that lack one,
> > you could use a simple lua filter.
> > 
> > Nick Moffitt <nick-iTLVOByc1N8@public.gmane.org> writes:
> > 
> > > Is there an easy way to specify that all code blocks (fenced, `inline`, etc) are treated by the same syntax highlighter?
> > >
> > > I am working on a document that has a lot of Scheme code, and it's rather infuriating to have to do things like `12`{.scheme} to get numbers formatted in paragraphs the way they are in the larger fenced code blocks.  I find myself taking shortcuts like `myfuncname` to save typing, but have to track down evry `else`{.scheme} so things are consistent.  I'm finding myself going mad when examples like `(this and that atom)` don't render the same as `(this and that atom)`{.scheme} because `and` is a reserved word.
> > >
> > > I'd find my document much easier to work on if I could just say "everyting in backticks is scheme.  Format it."
> > >
> > > -- 
> > > You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> > > To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > > To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/20201121173412.GP4166%40zork.net.
> 
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/20201121210354.GQ4166%40zork.net.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/20201121215008.GF4166%40zork.net.

Re: Default syntax for code blocks?

[John Gabriele]

On Sat, Nov 21, 2020, at 4:03 PM, Nick Moffitt wrote:
> I can't use indented code blocks inside of paragraphs, headings, and 
> definition lists, surely?
> 

Hi Nick,

Sorry to comment so late on this, but terminology note for posterity on this thread: "block" refers to what gives you a div (as opposed to a span). That is to say, there's two kinds of syntax here:

  * inline (`code`, *italics*, etc.) (for spans)
  * block (for divs), of which you have two kinds:
      + side-marked (indented, for code), `>` for blockquote
      + delimited, or "fenced" (`~~~for code blocks~~~` (or backticks))

-- John