From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: Auto width and height on table cells
Date: Thu, 30 Jun 2022 12:12:07 +0200 [thread overview]
Message-ID: <a0b6b2a0-fba0-298e-e78f-2ae3fd199c02@fiee.net> (raw)
In-Reply-To: <1f29574b-0153-da37-f72f-76a9d31fad69@xs4all.nl>
Am 30.06.22 um 09:36 schrieb Hans Hagen via ntg-context:
> On 6/30/2022 9:22 AM, Angel M Alganza via ntg-context wrote:
>>> They’re also tedious, because you can’t setup rows/columns in advance
>>> (like \setupTABLE) – or did that change?
>>
>> I'm afraid you're right.
> You're joking right? SInce when can one not set up something in some
> context subsystem? Why would I make a table mechanism with no presets?
Yes, presets are nice, and I appreciate the better performance, but if I
can setup stuff like striped tables or some other “advanced” formatting
without explicite settings within the table, I prefer that.
I can stay with “natural tables” (and “tabulate” for easy cases), but
the auto-stretching of rows or whole tables _is_ missing.
Unfortunately, this is a situation like in LaTeX: We have a choice of
table “packages”, but none of them covers my most common use cases.
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-06-30 10:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 5:43 Angel M Alganza via ntg-context
2022-06-30 6:16 ` Hans Hagen via ntg-context
2022-06-30 6:40 ` Angel M Alganza via ntg-context
2022-06-30 7:02 ` Henning Hraban Ramm via ntg-context
2022-06-30 7:22 ` Angel M Alganza via ntg-context
2022-06-30 7:36 ` Hans Hagen via ntg-context
2022-06-30 7:46 ` Angel M Alganza via ntg-context
2022-06-30 8:26 ` Hans Hagen via ntg-context
2022-06-30 8:37 ` Angel M Alganza via ntg-context
2022-06-30 14:15 ` Pablo Rodriguez via ntg-context
2022-06-30 16:10 ` Angel M Alganza via ntg-context
2022-06-30 16:44 ` Pablo Rodriguez via ntg-context
2022-06-30 10:12 ` Henning Hraban Ramm via ntg-context [this message]
2022-06-30 10:25 ` Angel M Alganza via ntg-context
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=a0b6b2a0-fba0-298e-e78f-2ae3fd199c02@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).