public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Rudi C <rudiwillalwaysloveyou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Isn’t there a plain text reader? Why?
Date: Fri, 16 Aug 2019 10:37:15 +0430	[thread overview]
Message-ID: <CAE9z9A1PhS=xsySFLDMNUf8SPogT2Ka9SCoWE41XHYjmeKZFoA@mail.gmail.com> (raw)
In-Reply-To: <4be8dffb-2e8c-3ba3-d584-a06928a48af7-Jdbf3xiKgS8@public.gmane.org>

[-- 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 --]

  parent reply	other threads:[~2019-08-16  6:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 17:08 Rudi C
     [not found] ` <255f893b-1048-4de9-aaeb-e9778187e701-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-15 17:29   ` Daniel Staal
     [not found]     ` <4be8dffb-2e8c-3ba3-d584-a06928a48af7-Jdbf3xiKgS8@public.gmane.org>
2019-08-16  6:07       ` Rudi C [this message]
     [not found]         ` <CAE9z9A1PhS=xsySFLDMNUf8SPogT2Ka9SCoWE41XHYjmeKZFoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-16 14:32           ` Daniel Staal
     [not found]             ` <08494ac8-209d-dfa6-43b6-f19034f2bef7-Jdbf3xiKgS8@public.gmane.org>
2019-08-17 14:34               ` Rudi C
     [not found]                 ` <CAE9z9A3zRg+9_v26kMR-9fb5HHykwQKDabiufWKSdHcNmMW0ag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-19 15:17                   ` Daniel Staal
2019-08-20  6:24                   ` John MacFarlane

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE9z9A1PhS=xsySFLDMNUf8SPogT2Ka9SCoWE41XHYjmeKZFoA@mail.gmail.com' \
    --to=rudiwillalwaysloveyou-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).