From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: ctxparskip is "Undefined control sequence" in project only
Date: Mon, 16 Jan 2012 13:01:41 +0100 [thread overview]
Message-ID: <08024CE0-D9C8-4377-8477-0763783E55DE@st.estfiles.de> (raw)
In-Reply-To: <4F140B54.9010201@wxs.nl>
Am 16.01.2012 um 12:34 schrieb Hans Hagen:
> On 16-1-2012 11:34, Steffen Wolfrum wrote:
>> Hi,
>>
>> here's another "Undefined control sequence" with recent beta:
>>
>> when using \ctxparskip in a project's component (see attached) the following error below pops up.
>> (When running the same example as a stand-alone-file it works fine!)
>>
>> Steffen
>>
>>
>> ! Undefined control sequence.
>>
>> system> tex> error on line 7 in file chap_X.tex: Undefined control sequence ...
>>
>> 1 %&context
>> 2 %!TEX TS-program = luatex
>> 3 \startcomponent chap_X
>> 4 \project MyProject
>> 5
>> 6
>> 7>> \startexdent
>> 8
>> 9 test
>> 10
>> 11 \stopexdent
>> 12
>> 13 \stopcomponent
>> 14
>>
>>
>> \117>exdent:before ->\ctxparskip
>
> Why don't you use \setupindenting?
To have discrete control over stretch tolerances, both baseline and parskip: plus XXpt minusYYpt
Steffen
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-01-16 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 10:34 Steffen Wolfrum
2012-01-16 11:34 ` Hans Hagen
2012-01-16 12:01 ` Steffen Wolfrum [this message]
2012-01-16 12:27 ` Hans Hagen
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=08024CE0-D9C8-4377-8477-0763783E55DE@st.estfiles.de \
--to=context@st.estfiles.de \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).