public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Question about pipe table column width explanation in manual
Date: Sat, 16 Jul 2022 09:52:44 +0200	[thread overview]
Message-ID: <9AFE0F49-CDAD-41DF-AE28-F22FF9AC70F3@gmail.com> (raw)
In-Reply-To: <CAMwawgPT52tgVBDhJWyX=ttgSaQYqVS2y4Wc9w3DfX08yqMAPw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>



> On Jul 15, 2022, at 12:16 PM, A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> Regarding pipe tables, the pandoc manual reads as follows:
> 
> If any line of the markdown source is longer than the column width (see –columns), then the table will take up the full text width and the cell contents will wrap (…)
> 
> The wording on this is quite unclear:
> 
> 	• What is meant by “any line of the markdown source”? Does that include lines which are not part of the table itself?


The source of the table is meant. If this confused you, feel free to submit a PR inserting "table's" before "markdown source."

> 	• What is meant by “the full text width”? Is it the width in the markdown source or the rendered version? Why should this have an impact on the table width?

The rendered version.  Table cells in the pandoc AST have widths which are represented as a fraction of the (rendered) text width.


-- 
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/9AFE0F49-CDAD-41DF-AE28-F22FF9AC70F3%40gmail.com.


      parent reply	other threads:[~2022-07-16  7:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 10:16 A A
     [not found] ` <CAMwawgPT52tgVBDhJWyX=ttgSaQYqVS2y4Wc9w3DfX08yqMAPw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-16  7:52   ` 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=9AFE0F49-CDAD-41DF-AE28-F22FF9AC70F3@gmail.com \
    --to=fiddlosopher-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).