From: Daniel Staal <DStaal-Jdbf3xiKgS8@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:32:22 -0400 [thread overview]
Message-ID: <08494ac8-209d-dfa6-43b6-f19034f2bef7@usa.net> (raw)
In-Reply-To: <CAE9z9A1PhS=xsySFLDMNUf8SPogT2Ka9SCoWE41XHYjmeKZFoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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.
next prev parent reply other threads:[~2019-08-16 14:32 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
[not found] ` <CAE9z9A1PhS=xsySFLDMNUf8SPogT2Ka9SCoWE41XHYjmeKZFoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-16 14:32 ` Daniel Staal [this message]
[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=08494ac8-209d-dfa6-43b6-f19034f2bef7@usa.net \
--to=dstaal-jdbf3xikgs8@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).