Isn’t there a plain text reader? Why?

Isn’t there a plain text reader? Why?

[Rudi C]

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

I want to read source code on my Kindle, and I was hoping to just use `pandoc -s -f txt *.py -o a.mobi` but it seems pandoc lacks a plain text reader?!

Re: Isn’t there a plain text reader? Why?

[Daniel Staal]

On 8/15/19 1:08 PM, Rudi C wrote:
> I want to read source code on my Kindle, and I was hoping to just use `pandoc -s -f txt *.py -o a.mobi` but it seems pandoc lacks a plain text reader?!
> 

Define plain text.  Do you just want it passed through with no changes? 
Do you want emphasis?  Do you want indents?  Do you want wrapping? 
Wrapping in some places but not others?

Pandoc reads several different formats that look like plain text.

In your case, I'd probably create a couple of files, each with just one 
line:

00000.py:
~~~{.python}

ZZZZZZ.py
~~~~

Then use `-f markdown` - that should enclose the whole thing inside a 
fenced code block and have it treat the interior as python code.

Daniel T. Staal

-- 
---------------------------------------------------------------
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------

Re: Isn’t there a plain text reader? Why?

[Rudi C]

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

I currently use a script to create a markdown with this structure:

# filename

```file-extension
file-content
```

# ...

Does your solution have advantages over this?
Btw, is there a table of supported things I can put after the triple `s?
Putting “el”, for example, did not activate EmacsLisp highlighting.

Ps: By plain text, I mean text that always wraps, and keeps its source
indentation. The kind of I thing I’ll see when I use `less` on a file.

On Thu, Aug 15, 2019 at 9:59 PM Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org> wrote:

> On 8/15/19 1:08 PM, Rudi C wrote:
> > I want to read source code on my Kindle, and I was hoping to just use
> `pandoc -s -f txt *.py -o a.mobi` but it seems pandoc lacks a plain text
> reader?!
> >
>
> Define plain text.  Do you just want it passed through with no changes?
> Do you want emphasis?  Do you want indents?  Do you want wrapping?
> Wrapping in some places but not others?
>
> Pandoc reads several different formats that look like plain text.
>
> In your case, I'd probably create a couple of files, each with just one
> line:
>
> 00000.py:
> ~~~{.python}
>
> ZZZZZZ.py
> ~~~~
>
> Then use `-f markdown` - that should enclose the whole thing inside a
> fenced code block and have it treat the interior as python code.
>
> Daniel T. Staal
>
> --
> ---------------------------------------------------------------
> This email copyright the author.  Unless otherwise noted, you
> are expressly allowed to retransmit, quote, or otherwise use
> the contents for non-commercial purposes.  This copyright will
> expire 5 years after the author's death, or in 30 years,
> whichever is longer, unless such a period is in excess of
> local copyright law.
> ---------------------------------------------------------------
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "pandoc-discuss" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/pandoc-discuss/DSRfQkWBlFE/unsubscribe.
> To unsubscribe from this group and all its topics, 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/4be8dffb-2e8c-3ba3-d584-a06928a48af7%40usa.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/CAE9z9A1PhS%3DxsySFLDMNUf8SPogT2Ka9SCoWE41XHYjmeKZFoA%40mail.gmail.com.

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

Re: Isn’t there a plain text reader? Why?

[Daniel Staal]

On 8/16/19 2:07 AM, Rudi C wrote:
> I currently use a script to create a markdown with this structure:
> 
> # filename
> 
> ```file-extension
> file-content
> ```
> 
> # ...
> 
> Does your solution have advantages over this?
> Btw, is there a table of supported things I can put after the triple `s? 
> Putting “el”, for example, did not activate EmacsLisp highlighting.

No real advantages over this - it's basically an alternate syntax for 
the same thing.

There's no reference table, as it depends on the compile - however you 
can get the list for the current install with:

`pandoc --list-highlight-languages`

> Ps: By plain text, I mean text that always wraps, and keeps its source 
> indentation. The kind of I thing I’ll see when I use `less` on a file.

The point I was trying to make is that 'plain text' isn't a very 
well-defined term, or a structured input language.  Pandoc deals with 
structured input, and has several input formats that could reasonably 
handle random text - but unstructured text is a bit out of Pandoc's scope.

You're not dealing with unstructured text however - you're working with 
source code, and again Pandoc can handle source code in several formats 
- Markdown being the best supported and documented.

Daniel T. Staal

-- 
---------------------------------------------------------------
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------

-- 
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/08494ac8-209d-dfa6-43b6-f19034f2bef7%40usa.net.

Re: Isn’t there a plain text reader? Why?

[Rudi C]

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

Thank you!
I imagine there are aliases defined for `pandoc
--list-highlight-languages`? Since specifying `py` seemed to work just as
well as `python`, if I'm remembering correctly. If so, where should I edit
in the sources ti add more aliases? (And send those edits as PRs)(Like,
`el` could be an alias for `commonlisp` ...)

On Fri, Aug 16, 2019 at 7:02 PM Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org> wrote:

> On 8/16/19 2:07 AM, Rudi C wrote:
> > I currently use a script to create a markdown with this structure:
> >
> > # filename
> >
> > ```file-extension
> > file-content
> > ```
> >
> > # ...
> >
> > Does your solution have advantages over this?
> > Btw, is there a table of supported things I can put after the triple `s?
> > Putting “el”, for example, did not activate EmacsLisp highlighting.
>
> No real advantages over this - it's basically an alternate syntax for
> the same thing.
>
> There's no reference table, as it depends on the compile - however you
> can get the list for the current install with:
>
> `pandoc --list-highlight-languages`
>
> > Ps: By plain text, I mean text that always wraps, and keeps its source
> > indentation. The kind of I thing I’ll see when I use `less` on a file.
>
> The point I was trying to make is that 'plain text' isn't a very
> well-defined term, or a structured input language.  Pandoc deals with
> structured input, and has several input formats that could reasonably
> handle random text - but unstructured text is a bit out of Pandoc's scope.
>
> You're not dealing with unstructured text however - you're working with
> source code, and again Pandoc can handle source code in several formats
> - Markdown being the best supported and documented.
>
> Daniel T. Staal
>
> --
> ---------------------------------------------------------------
> This email copyright the author.  Unless otherwise noted, you
> are expressly allowed to retransmit, quote, or otherwise use
> the contents for non-commercial purposes.  This copyright will
> expire 5 years after the author's death, or in 30 years,
> whichever is longer, unless such a period is in excess of
> local copyright law.
> ---------------------------------------------------------------
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "pandoc-discuss" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/pandoc-discuss/DSRfQkWBlFE/unsubscribe.
> To unsubscribe from this group and all its topics, 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/08494ac8-209d-dfa6-43b6-f19034f2bef7%40usa.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/CAE9z9A3zRg%2B9_v26kMR-9fb5HHykwQKDabiufWKSdHcNmMW0ag%40mail.gmail.com.

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

Re: Isn’t there a plain text reader? Why?

[Daniel Staal]

On 8/17/19 10:34 AM, Rudi C wrote:
> Thank you!
> I imagine there are aliases defined for `pandoc 
> --list-highlight-languages`? Since specifying `py` seemed to work just 
> as well as `python`, if I'm remembering correctly. If so, where should I 
> edit in the sources ti add more aliases? (And send those edits as 
> PRs)(Like, `el` could be an alias for `commonlisp` ...)

I haven't played with it to much at the moment - I assume that's part of 
the Skylighting package.

Here's Pandoc's docs on highlighting, with links to how to create your 
own, and to the highlighting package it uses:
<https://pandoc.org/MANUAL.html#syntax-highlighting>

Daniel T. Staal

-- 
---------------------------------------------------------------
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------

Re: Isn’t there a plain text reader? Why?

[John MacFarlane]

Yes, generally you can use either the canonical language name
(as listed by --list-highlight-languages) or standard file
extensions (like py).

If you look at the xml syntax descriptions here
https://github.com/jgm/skylighting/tree/master/skylighting-core/xml
you'll see (on the language element) the attribute "extensions";
this is where the accepted extensions come from.

Rudi C <rudiwillalwaysloveyou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Thank you!
> I imagine there are aliases defined for `pandoc
> --list-highlight-languages`? Since specifying `py` seemed to work just as
> well as `python`, if I'm remembering correctly. If so, where should I edit
> in the sources ti add more aliases? (And send those edits as PRs)(Like,
> `el` could be an alias for `commonlisp` ...)
>
> On Fri, Aug 16, 2019 at 7:02 PM Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org> wrote:
>
>> On 8/16/19 2:07 AM, Rudi C wrote:
>> > I currently use a script to create a markdown with this structure:
>> >
>> > # filename
>> >
>> > ```file-extension
>> > file-content
>> > ```
>> >
>> > # ...
>> >
>> > Does your solution have advantages over this?
>> > Btw, is there a table of supported things I can put after the triple `s?
>> > Putting “el”, for example, did not activate EmacsLisp highlighting.
>>
>> No real advantages over this - it's basically an alternate syntax for
>> the same thing.
>>
>> There's no reference table, as it depends on the compile - however you
>> can get the list for the current install with:
>>
>> `pandoc --list-highlight-languages`
>>
>> > Ps: By plain text, I mean text that always wraps, and keeps its source
>> > indentation. The kind of I thing I’ll see when I use `less` on a file.
>>
>> The point I was trying to make is that 'plain text' isn't a very
>> well-defined term, or a structured input language.  Pandoc deals with
>> structured input, and has several input formats that could reasonably
>> handle random text - but unstructured text is a bit out of Pandoc's scope.
>>
>> You're not dealing with unstructured text however - you're working with
>> source code, and again Pandoc can handle source code in several formats
>> - Markdown being the best supported and documented.
>>
>> Daniel T. Staal
>>
>> --
>> ---------------------------------------------------------------
>> This email copyright the author.  Unless otherwise noted, you
>> are expressly allowed to retransmit, quote, or otherwise use
>> the contents for non-commercial purposes.  This copyright will
>> expire 5 years after the author's death, or in 30 years,
>> whichever is longer, unless such a period is in excess of
>> local copyright law.
>> ---------------------------------------------------------------
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "pandoc-discuss" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/pandoc-discuss/DSRfQkWBlFE/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/08494ac8-209d-dfa6-43b6-f19034f2bef7%40usa.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/CAE9z9A3zRg%2B9_v26kMR-9fb5HHykwQKDabiufWKSdHcNmMW0ag%40mail.gmail.com.

-- 
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/m2mug4iccb.fsf%40johnmacfarlane.net.