Literate haskell & #-style headers

Literate haskell & #-style headers

[Conal Elliott]

[-- Attachment #1: Type: text/plain, Size: 679 bytes --]

Does anyone know how to use #-style markdown headers without ghc choking on
them (as preprocessor directives)? I can use the underline variant for 1st &
2nd level headings ("-----" and "====="), but I often like more deeply
nested headings.

Thanks,  - Conal

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en.


[-- Attachment #2: Type: text/html, Size: 738 bytes --]

Re: Literate haskell & #-style headers

[Ivan Lazar Miljenovic]

On 12 November 2010 07:19, Conal Elliott <conal-R2YG1wQAgWFeoWH0uzbU5w@public.gmane.org> wrote:
> Does anyone know how to use #-style markdown headers without ghc choking on
> them (as preprocessor directives)? I can use the underline variant for 1st &
> 2nd level headings ("-----" and "====="), but I often like more deeply
> nested headings.

I haven't; in the end I resorted to using ---- and ====.  One
alternative I thought of (but never got around to implementing, since
I wasn't sure how to get it to work for other markdown-laden modules
that are imported) is to use a wrapper around ghci to strip out all
the non-markdown stuff.

-- 
Ivan Lazar Miljenovic
Ivan.Miljenovic-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
IvanMiljenovic.wordpress.com

Re: Literate haskell & #-style headers

[Ivan Lazar Miljenovic]

On 12 November 2010 11:58, Ivan Lazar Miljenovic
<ivan.miljenovic-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> I haven't; in the end I resorted to using ---- and ====.  One
> alternative I thought of (but never got around to implementing, since
> I wasn't sure how to get it to work for other markdown-laden modules
> that are imported) is to use a wrapper around ghci to strip out all
> the non-markdown stuff.

I of course meant the non-haskell stuff, not the non-markdown stuff.

-- 
Ivan Lazar Miljenovic
Ivan.Miljenovic-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
IvanMiljenovic.wordpress.com

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en.

Re: Literate haskell & #-style headers

[John MacFarlane]

+++ Conal Elliott [Nov 11 10 12:19 ]:
>    Does anyone know how to use #-style markdown headers without ghc
>    choking on them (as preprocessor directives)? I can use the underline
>    variant for 1st & 2nd level headings ("-----" and "====="), but I often
>    like more deeply nested headings.
>    Thanks,  - Conal

As far as I know, there's no way to do this, which is irritating.

Re: Literate haskell & #-style headers

[John MacFarlane]

+++ Conal Elliott [Nov 11 10 12:19 ]:
>    Does anyone know how to use #-style markdown headers without ghc
>    choking on them (as preprocessor directives)? I can use the underline
>    variant for 1st & 2nd level headings ("-----" and "====="), but I often
>    like more deeply nested headings.

Remember that if your target is HTML, you can always use

<h3>heading</h3>

Ideally pandoc should parse these as Headers, rather than raw HTML.
There's already a bug report to this effect.

John

Re: Literate haskell & #-style headers

[Aditya Mahajan]

On Thu, 11 Nov 2010, John MacFarlane wrote:

> +++ Conal Elliott [Nov 11 10 12:19 ]:
>>    Does anyone know how to use #-style markdown headers without ghc
>>    choking on them (as preprocessor directives)? I can use the underline
>>    variant for 1st & 2nd level headings ("-----" and "====="), but I often
>>    like more deeply nested headings.
>>    Thanks,  - Conal
>
> As far as I know, there's no way to do this, which is irritating.

How about introducing a Markdown extension that treats ~~~~~~~~ as the 
third level heading, just like rst.

Aditya

Re: Literate haskell & #-style headers

[Tillmann Rendel]

Hi,

Aditya Mahajan wrote:
> How about introducing a Markdown extension that treats ~~~~~~~~ as the
> third level heading, just like rst.

I would like to see more "====="-style headings, so that large documents 
with complex structure can be written with "====="-style headings. And 
indeed, I can easily  think of a hierarchy of ten different 
"====="-style headings:

> Level 1
> =======
>
> Level 2
> = = = =
>
> Level 3
> -------
>
> Level 4
> - - - -
>
> Level 5
> ~~~~~~~
>
> Level 6
> ~ ~ ~ ~
>
> Level 7
> :::::::
>
> Level 8
> : : : :
>
> Level 9
> .......
>
> Level 10
> . . . .

Now, this (or something similar) might be good for documents which 
actually need 10 levels of headings, but what about documents which 
don't? It would be annoying to use "=====" and "= = = =" for simple 
documents with two levels of headings. Instead, we clearly want to use 
the old "=====" and "-----" for such documents. (And also for backwards 
compatibility).

I therefore propose to use the list of heading levels only for 
structuring the document into a tree of sections, and then walk through 
that tree and assign consistent heading levels.

For example, the document

> A section
> =========
>
> A subsection
> ~~~~~~~~~~~~
>
> Another subsection
> ~~~~~~~~~~~~~~~~~~
>
> Another section
> ===============
>
> A subsection
> - - - - - -
>
> A subsubsection
> ~~~~~~~~~~~~~~~

would be parsed as the following tree

1.     A Section
1.1    A Subsection
1.2    Another Subsection
2.     Another Section
2.1    A subsection
2.1.1  A subsubsection

and then transformed into the following.

> <h1>A section</h1>
> <h2>A subsection</h2>
> <h2>Another subsection</h2>
> <h1>Another section</h1>
> <h2>A subsection</h2>
> <h3>A subsubsection</h3>

Note how there is no fixed association between underlining style and 
heading level.

I think this would be mostly backwards compatible. The only possibly 
problematic thing I can think of: If a document contains "----"-headings 
before the first "===="-heading, these "----"-headings would be parsed 
as level 2-headings currently, but as level 1-headings in my proposal.

But this would enable users to use whatever heading style fits their 
needs, *locally* to the section at hand. This is especially usefull if 
independently written documents are to be composed into a single 
document, like assembling a number of blog posts into a larger tutorial, 
or a number of research papers into a cumulative thesis.

   Tillmann

Re: Literate haskell & #-style headers

[John MacFarlane]

> I therefore propose to use the list of heading levels only for
> structuring the document into a tree of sections, and then walk
> through that tree and assign consistent heading levels.

This is how reStructuredText works -- but I don't want to
do that in pandoc's markdown reader, because it's not backwards
compatible with markdown.

John
 

Re: Literate haskell & #-style headers

[Conal Elliott]

[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]

Here's a half-baked idea: When the input language is markdown+lhs, allow
#-style header to begin with a blank space.  Then ghc will treat such lines
as comments, while pandoc will treat them as headers.

Thoughts?

   - Conal

On Thu, Nov 11, 2010 at 7:49 PM, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>wrote:

> +++ Conal Elliott [Nov 11 10 12:19 ]:
> >    Does anyone know how to use #-style markdown headers without ghc
> >    choking on them (as preprocessor directives)? I can use the underline
> >    variant for 1st & 2nd level headings ("-----" and "====="), but I
> often
> >    like more deeply nested headings.
> >    Thanks,  - Conal
>
> As far as I know, there's no way to do this, which is irritating.
>
> --
> You received this message because you are subscribed to the Google Groups
> "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to
> pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
> .
> For more options, visit this group at
> http://groups.google.com/group/pandoc-discuss?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en.


[-- Attachment #2: Type: text/html, Size: 2300 bytes --]

Re: Literate haskell & #-style headers

[Ivan Lazar Miljenovic]

On 13 November 2010 15:02, Conal Elliott <conal-R2YG1wQAgWFeoWH0uzbU5w@public.gmane.org> wrote:
> Here's a half-baked idea: When the input language is markdown+lhs, allow
> #-style header to begin with a blank space.  Then ghc will treat such lines
> as comments, while pandoc will treat them as headers.

That's not the only problem with ghc and markdown+lhs...

If you use bird-track style literate haskell, then  you can't use >
for quotes.  Furthermore, you have to remember to leave a blank line
before and after code if you're putting them inside ~~~~~ ... ~~~~~
-style code blocks.

As such, I wonder if it's possible we could get approved "Markdown
Haskell" in Haskell2011 or something such that it only cares about
code in such code blocks, maybe giving it a new extension if required.
 It probably won't happen though...

-- 
Ivan Lazar Miljenovic
Ivan.Miljenovic-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
IvanMiljenovic.wordpress.com

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en.

Re: Literate haskell & #-style headers

[Conal Elliott]

[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]

On Fri, Nov 12, 2010 at 11:34 PM, Ivan Lazar Miljenovic <
ivan.miljenovic-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> On 13 November 2010 15:02, Conal Elliott <conal-R2YG1wQAgWFeoWH0uzbU5w@public.gmane.org> wrote:
> > Here's a half-baked idea: When the input language is markdown+lhs, allow
> > #-style header to begin with a blank space.  Then ghc will treat such
> lines
> > as comments, while pandoc will treat them as headers.
>
> That's not the only problem with ghc and markdown+lhs...
>
> If you use bird-track style literate haskell, then  you can't use >
> for quotes.


You can't use ">" for quotes *unless* you precede the ">" by a space
character (i.e., " >"). I still have a hard time remembering the space.


>  Furthermore, you have to remember to leave a blank line
> before and after code if you're putting them inside ~~~~~ ... ~~~~~
> -style code blocks.
>
> As such, I wonder if it's possible we could get approved "Markdown
> Haskell" in Haskell2011 or something such that it only cares about
> code in such code blocks, maybe giving it a new extension if required.
>  It probably won't happen though...
>

Probably not unless there is more interest in markdown-based literate
Haskell programming than I've noticed so far.

   - Conal

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en.


[-- Attachment #2: Type: text/html, Size: 2404 bytes --]

Re: Literate haskell & #-style headers

[Jeremy Shaw]

[-- Attachment #1: Type: text/plain, Size: 2422 bytes --]

Has there been any progress made on this? I have the same exact problem. 
Seems like there were some good ideas in this thread, but I don't see 
anything in the manual about them being implemented.

In my case, I am willing to use the pandoc scripting API to do a 
transformation.. but I am not really clear the best way to approach that. 
If I create a new header style.. I think it will just show up as 
undifferentiated RawInline or Str or something? So.. then I am left doing 
sed-style text replacement?

- jeremy

On Saturday, November 13, 2010 12:03:32 PM UTC-6, Conal wrote:
>
> On Fri, Nov 12, 2010 at 11:34 PM, Ivan Lazar Miljenovic <
> ivan.mi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> wrote:
>
>> On 13 November 2010 15:02, Conal Elliott <co...-R2YG1wQAgWFeoWH0uzbU5w@public.gmane.org <javascript:>> 
>> wrote:
>> > Here's a half-baked idea: When the input language is markdown+lhs, allow
>> > #-style header to begin with a blank space.  Then ghc will treat such 
>> lines
>> > as comments, while pandoc will treat them as headers.
>>
>> That's not the only problem with ghc and markdown+lhs...
>>
>> If you use bird-track style literate haskell, then  you can't use >
>> for quotes.
>
>
> You can't use ">" for quotes *unless* you precede the ">" by a space 
> character (i.e., " >"). I still have a hard time remembering the space.
>  
>
>>  Furthermore, you have to remember to leave a blank line
>> before and after code if you're putting them inside ~~~~~ ... ~~~~~
>> -style code blocks.
>>
>> As such, I wonder if it's possible we could get approved "Markdown
>> Haskell" in Haskell2011 or something such that it only cares about
>> code in such code blocks, maybe giving it a new extension if required.
>>  It probably won't happen though...
>>
>
> Probably not unless there is more interest in markdown-based literate 
> Haskell programming than I've noticed so far.
>
>    - Conal
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msg/pandoc-discuss/-/5twemoDKuAYJ.
For more options, visit https://groups.google.com/groups/opt_out.



[-- Attachment #2: Type: text/html, Size: 3359 bytes --]

Re: Literate haskell & #-style headers

[John MacFarlane]

+++ Jeremy Shaw [Dec 12 12 17:01 ]:
>    Has there been any progress made on this? I have the same exact
>    problem. Seems like there were some good ideas in this thread, but I
>    don't see anything in the manual about them being implemented.

It would not be too hard to implement one of these proposals.  I
wouldn't want to alter standard markdown parsing, but I suppose I
could make the changes work only with literate Haskell...

>    In my case, I am willing to use the pandoc scripting API to do a
>    transformation.. but I am not really clear the best way to approach
>    that. If I create a new header style.. I think it will just show up as
>    undifferentiated RawInline or Str or something? So.. then I am left
>    doing sed-style text replacement?

If you're targeting HTML, you can just use raw HTML h3 tags...

John