ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sietse Brouwer <sbbrouwer@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: next beta
Date: Tue, 19 Mar 2013 23:46:35 +0100	[thread overview]
Message-ID: <CAF=dkzwu4kGPHMJkqpVjSuKP4G=aUvpvDcGcF91J=LbjU2N-Sg@mail.gmail.com> (raw)
In-Reply-To: <5148DFF3.3020705@wxs.nl>

> i.e. we already had CL CM and CR, so CT is new .. should be wikified.

The wiki [1] describes these \C* commands:

\CR 	 color is applied to the background of the text and the remaining
space on the right;
\CC 	 color is applied to the background of the text only;
\CM 	 color is applied to the background of the text and the remaining
space on both sides;
\CL 	 color is applied to the background of the text and the remaining
space on the left.

[1] http://wiki.contextgarden.net/Tabulate

What does CT do differently than CC? It's not quite clear from the example.

Cheers,

Sietse
___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2013-03-19 22:46 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 22:00 Hans Hagen
2013-03-19 22:46 ` Sietse Brouwer [this message]
2013-03-19 23:03   ` Hans Hagen
2013-03-20  7:14   ` Keith J. Schultz
2013-03-20  8:43     ` Hans Hagen
2013-03-20 16:36       ` Jonathan Barchi
2013-03-20 20:27         ` Hans Hagen
2013-03-20  7:24   ` next beta (tabulate) Alan BRASLAU
2013-03-20  9:42     ` Hans Hagen
2015-04-15 17:08 ` next beta Aditya Mahajan
2015-04-16 12:45   ` Hans Hagen
2013-05-28 11:07 Hans Hagen
2015-04-15  9:05 Hans Hagen
2016-02-25 10:47 Hans Hagen
2016-03-03 17:34 Hans Hagen
2016-06-27  8:38 Hans Hagen
2016-06-27 10:28 ` Meer, Hans van der
2017-01-15 16:19 Hans Hagen
2017-01-17 19:13 ` Henri Menke
2017-01-17 19:23   ` Hans Hagen
2017-01-17 19:27     ` Henri Menke
2017-01-17 19:51       ` Hans Hagen
2017-06-12 15:25 Hans Hagen
2017-06-12 15:56 ` Mathias Schickel
2017-06-12 16:17   ` Hans Hagen
2017-06-13 11:18     ` Mathias Schickel
2017-06-13 14:46       ` Hans Hagen
2017-06-13 15:52         ` Mohammad Hossein Bateni
2017-06-13 16:18         ` Aditya Mahajan
2017-06-14  9:33         ` Mathias Schickel
2017-06-14 11:23           ` Hans Hagen
2017-06-13  6:06 ` Aditya Mahajan
2017-06-13  8:05   ` Hans Hagen
2017-06-13 12:47 ` Hans Åberg
     [not found] <mailman.575.1497365252.2080.ntg-context@ntg.nl>
2017-06-17 13:48 ` Jeong Dal
2017-06-18 11:00   ` Hans Hagen
2017-06-18 15:39     ` Jeong Dal
2017-06-18 22:56     ` Henri Menke
2017-06-19  7:36       ` Hans Hagen
2017-06-19  7:44         ` Aditya Mahajan
2018-04-14 16:51 Hans Hagen
2018-04-18  6:34 ` Otared Kavian

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='CAF=dkzwu4kGPHMJkqpVjSuKP4G=aUvpvDcGcF91J=LbjU2N-Sg@mail.gmail.com' \
    --to=sbbrouwer@gmail.com \
    --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).