From: "ivo....-xwz7R8GQi1g@public.gmane.org" <ivo.welch-xwz7R8GQi1g@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: finicky pandoc tables
Date: Mon, 20 Jun 2022 11:35:41 -0700 (PDT) [thread overview]
Message-ID: <fa76e518-7408-4fe6-8de6-0150af1177f1n@googlegroups.com> (raw)
In-Reply-To: <87ilovon8a.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1434 bytes --]
would it be possible to allow for a generic syntax that encompasses
(allows) both types of tables --- or does one fundamentally violate the
other?
/iaw
On Sunday, June 19, 2022 at 11:36:31 PM UTC-7 Albert Krewinkel wrote:
>
> "ivo....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <ivo....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > pandoc 2.18, macOS. I find the tables to be very finicky, rather than
> > very intuitive. for example,
> >
> > [...]
>
> The issue, as far as I can see, is that the tables are a mix of grid
> tables and pipe tables. Try to either
>
> - Remove all horizontal lines except for the one separating table head
> and body. Use `-` (not `=`) for that line.
>
> - Alternatively, add `+--+` lines between all rows.
>
> Currently you have a table with a single body row, so all text in a
> column is in a single cell. That's why some text is moved around if the
> cell width permits to do so.
>
> HTH
>
> --
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>
--
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/fa76e518-7408-4fe6-8de6-0150af1177f1n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2192 bytes --]
next prev parent reply other threads:[~2022-06-20 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 20:51 ivo....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <940779e4-0ae1-46fc-9270-af8b73f1131en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-20 6:28 ` Albert Krewinkel
[not found] ` <87ilovon8a.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-20 18:35 ` ivo....-xwz7R8GQi1g@public.gmane.org [this message]
[not found] ` <fa76e518-7408-4fe6-8de6-0150af1177f1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-23 19:32 ` Albert Krewinkel
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=fa76e518-7408-4fe6-8de6-0150af1177f1n@googlegroups.com \
--to=ivo.welch-xwz7r8gqi1g@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).