From: Norbert Lange <nolange79-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: getting pandoc to always use pipe_tables
Date: Thu, 22 Mar 2018 11:13:49 -0700 (PDT) [thread overview]
Message-ID: <a58b7f3a-bba4-42e9-98c5-26bb45c11f49@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1628 bytes --]
Hello,
I am also using pandoc as code-format, measns I will write really sloppy
tables and expect pandoc to sort everything out.
For easier editing (and automatic reformating) I prefer pipe_tables.
The issue now arises when a pipe_table has more content than what would fit
one one line,
pandoc will not use pipe_tables, but fall back to inline html.
is there any way to restrict pandoc to always use pipe_tables?
echo '||||
|-----|-----|-----|
something rather long | and has a windy descripton | I cant bring my self
to format this manually
pandoc|is so great that it can fix everything|
bug|but it wont currently|' | pandoc -t
markdown-simple_tables-multiline_tables-grid_tables+pipe_tables -
pandoc 2.1.3
Compiled with pandoc-types 1.17.4.2, texmath 0.10.1.1, skylighting 0.7.0.2
Default user data directory: /home/lano/.pandoc
Copyright (C) 2006-2018 John MacFarlane
Web: http://pandoc.org
This is free software; see the source for copying conditions.
There is no warranty, not even for merchantability or fitness
for a particular purpose.
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a58b7f3a-bba4-42e9-98c5-26bb45c11f49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2337 bytes --]
next reply other threads:[~2018-03-22 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 18:13 Norbert Lange [this message]
[not found] ` <a58b7f3a-bba4-42e9-98c5-26bb45c11f49-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-03-22 19:27 ` Daniel Staal
[not found] ` <ccf0e8b4-5232-bde3-c8be-6d012624d4ff-Jdbf3xiKgS8@public.gmane.org>
2018-03-26 13:26 ` Norbert Lange
2018-03-22 21:39 ` 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=a58b7f3a-bba4-42e9-98c5-26bb45c11f49@googlegroups.com \
--to=nolange79-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).