From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TABLE setups
Date: Sun, 29 Jul 2018 13:36:08 +0200 [thread overview]
Message-ID: <E1B3A7DA-DCED-493A-BD21-8AF612D4FB9C@fiee.net> (raw)
In-Reply-To: <69B2743A-96C3-401F-82B2-1CCB7AD98EB4@fiee.net>
Am 2018-07-28 um 11:09 schrieb Henning Hraban Ramm <texml@fiee.net>:
>>> Or can I go via setups like \bTABLE[setups=mystyle] ?
>>
>> \startsetups mystyle
>> \setupTABLE[frame=off]
>> \setupTABLE[row][first][topframe=on,bottomframe=on,style=bold]
>> \setupTABLE[row][last] [bottomframe=on]
>> \stopsetups
>> \starttext
>>
>> \bTABLE[setups=mystyle]
>
> Thank you, that was what I wanted to know. A one-line answer would have been enough ;)
So finally I get the hang of setups, and natural tables do what I want, except:
How can I convince my TABLEs, that there should be an empty line before them??
\setupTABLE[before={\blank[2*big]}]
doesn’t do anything.
I tried \vskip, but that somehow kills part of the setup.
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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:[~2018-07-29 11:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 19:38 Henning Hraban Ramm
2018-07-28 1:35 ` Henri Menke
2018-07-28 9:09 ` Henning Hraban Ramm
2018-07-29 9:16 ` Hans Hagen
2018-07-29 11:36 ` Henning Hraban Ramm [this message]
2018-07-29 12:43 ` Henning Hraban Ramm
2018-07-30 14:22 ` kaddour kardio
2018-07-30 15:41 ` Henning Hraban Ramm
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=E1B3A7DA-DCED-493A-BD21-8AF612D4FB9C@fiee.net \
--to=texml@fiee.net \
--cc=ntg-context@ntg.nl \
/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).