From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Table column width in pipe tables
Date: Wed, 29 Jun 2016 11:06:40 -0700 [thread overview]
Message-ID: <20160629180640.GA72535@protagoras.berkeley.edu> (raw)
In-Reply-To: <1c7d17cc-62a4-47c5-a7ac-cc3594bdd3fd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
If you're targeting HTML, you could just use CSS.
If all the tables in your document should have the same
column widths, just set a fixed width for td.
If you want this to affect only some tables, you could
wrap these tables in a div (assuming you're using the
markdown_in_html_blocks or native_divs extension).
Or, use pandoc multiline tables.
+++ Adam Rice [Jun 29 16 10:39 ]:
> I also use pipe tables a lot, and I've encountered a related issue.
> I have a document with a series of similar pipe tables (same column
> headers, different content). I would like for them to all have the same
> column widths for visual consistency. So far, I haven't found the magic
> combination of table separators and/or pandoc command options that will
> force this behavior. I've also started playing with inserting HTML
> directly into the Markdown, but that kind of undermines the point.
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/1c7d17cc-62a4-47c5-
> a7ac-cc3594bdd3fd%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/1c7d17cc-62a4-47c5-a7ac-cc3594bdd3fd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
prev parent reply other threads:[~2016-06-29 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 1:03 news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA
[not found] ` <470f5401-a92d-4955-aff6-d7f242b2cbd9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-04-08 22:00 ` John MacFarlane
[not found] ` <20160408220003.GC61469-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org>
2016-06-29 17:39 ` Adam Rice
[not found] ` <1c7d17cc-62a4-47c5-a7ac-cc3594bdd3fd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-06-29 18:06 ` John MACFARLANE [this message]
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=20160629180640.GA72535@protagoras.berkeley.edu \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).