From: Elliot Clifton <cliftoo@gmail.com>
Subject: Re: ntg-context Digest, Vol 20, Issue 20
Date: Sat, 11 Feb 2006 16:42:41 +0000 [thread overview]
Message-ID: <e65d34bf0602110842w6c2eb268v@mail.gmail.com> (raw)
In-Reply-To: <mailman.1.1139396401.14319.ntg-context@ntg.nl>
On 08/02/06, Hans Hagan wrote:
> > Regardless of the table column format I specify, paragraphs remain
> > justified this is not what I want.
> >
> hm, can you give an example of usage?
>
> Hans
\starttable[|l p(2cm)| l p(5cm)]
\NC System1 \NC SubsystemA, SubsystemC, SubsystemD, SubsystemE,
SubsystemF, etc. \AR
\NC System2 \NC SubsystemA, SubsystemC, SubsystemD, SubsystemE,
SubsystemF, etc. \AR
\NC System3 \NC SubsystemA, SubsystemC, SubsystemD,
SubsystemE, SubsystemF, etc. \AR
\stoptable
It works this sample text but doesn't work actual text I want to use.
I do not want to post this information in a public forum, can I sed it
to you personally?
Elliot
parent reply other threads:[~2006-02-11 16:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.1.1139396401.14319.ntg-context@ntg.nl>]
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=e65d34bf0602110842w6c2eb268v@mail.gmail.com \
--to=cliftoo@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).