From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Anton Sharonov
<anton.sharonov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: line breaking in grid table cells
Date: Wed, 09 Jun 2021 15:26:29 -0700 [thread overview]
Message-ID: <m2v96mvfmy.fsf@MacBook-Pro-2.hsd1.ca.comcast.net> (raw)
In-Reply-To: <CAMoRF4n_mvcVJ6pW9N7xbjrvc3msnzWcG4D9WoiY+WFqjGD5iQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Anton Sharonov <anton.sharonov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Said that, my vote goes as +1 to "make it an option".
>
> Arguments:
>
> Like it is now - breaking the verbatim content looks ugly of course.
> But expanding column sizes potentially leads to very wide total table
> width, hard to read and maintain - which in my opinion is even more
> ugly. So +1 for to make it an option - at least allow to keep current
> status quo.
Agreed that the widened cells would be ugly. But, breaking the
URLs or verbatim content changes the meaning and makes them
unusable. Given this choice, wouldn't everyone prefer "ugly"?
Especially if they're given a warning which allows them to
make adjustments to the table to make it look nicer?
Simplicity is better in general, so I lean towards not making
it an option until I see a good reason why people might prefer
beautiful+broken to ugly+working.
prev parent reply other threads:[~2021-06-09 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 14:44 John MacFarlane
[not found] ` <m2o8cf9jy7.fsf-jF64zX8BO0+iXxlc9qkzFr9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-06-09 21:18 ` Anton Sharonov
[not found] ` <CAMoRF4n_mvcVJ6pW9N7xbjrvc3msnzWcG4D9WoiY+WFqjGD5iQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-09 22:26 ` 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=m2v96mvfmy.fsf@MacBook-Pro-2.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=anton.sharonov-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).