From: news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Table column width in pipe tables
Date: Wed, 6 Apr 2016 18:03:29 -0700 (PDT) [thread overview]
Message-ID: <470f5401-a92d-4955-aff6-d7f242b2cbd9@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1595 bytes --]
I'm using pipe tables like
| Key combo | Description |
| --- | --- |
| Shift + Cmd + arrows up/down | go through MoneyWiz sections such as
Accounts, Dashboard, Budgets, Reports, etc. |
quite a bit.
(1) However I do not understand the logic *how the width of the table
columns is determined*. In the case above the 2nd column will be extremely
narrow.
I can rectify this by longer dash lines like
| --------- | --------- |
But why? And how long do I have to make them? (I would have thought the
*relative* length would be used; so in the case of the dash line
| --- | --- |
each column would get a max of 50%.)
(2) The documentation says:
If a pipe table contains a row whose printable content is wider than the
column width (see --columns), then the cell contents will wrap, with the
relative cell widths determined by the widths of the separator lines.
However elsewhere the doco states that --columns "affects only the
generated source code". So what's the logic and mechanism here?
Many thanks,
Leo
--
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/470f5401-a92d-4955-aff6-d7f242b2cbd9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 3186 bytes --]
next reply other threads:[~2016-04-07 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 1:03 news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA [this message]
[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
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=470f5401-a92d-4955-aff6-d7f242b2cbd9@googlegroups.com \
--to=news-wptjrydoupgeaopm6fajmqkbcandltla@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).