From: Peter Rolf <indiego@gmx.net>
Subject: Re: problem with \startnarrower (?)
Date: Tue, 21 Nov 2006 22:26:40 +0100 [thread overview]
Message-ID: <45636F10.1010203@gmx.net> (raw)
In-Reply-To: <EA4CE56F-C523-454D-B697-574DD153DD74@princeton.edu>
Alan Bowen wrote:
> There seems to be a change in latest ConTeXt (ver: 2006.11.20 09:49
> MK II fmt: 2006.11.20 int: english/english) that has broken my
> definitions for setting extracts in the body text.
>
> \defineblank[extractdistance][3pt]
>
> \definestartstop[extract][
> before={[extractdistance]
> \setupnarrower[left=1.5pc,right=1.5pc]
> \startnarrower[left,right]
> \noindent},
> after={\stopnarrower
> \blank[extractdistance]
> \indenting[yes]}]
>
> \starttext
>
> Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Morbi
> commodo, ipsum sed pharetra gravida, orci magna rhoncus neque, id
> pulvinar odio lorem non turpis. Nullam sit amet enim. Suspendisse id
> velit vitae ligula volutpat condimentum.
> \startextract
> Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Morbi
> commodo, ipsum sed pharetra gravida, orci magna rhoncus neque,
> id pulvinar odio lorem non turpis. Nullam sit amet enim.
> Suspendisse id velit vitae ligula volutpat condimentum.
> \stopextract
> Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Morbi
> commodo, ipsum sed pharetra gravida, orci magna rhoncus neque, id
> pulvinar odio lorem non turpis. Nullam sit amet enim.
>
> \stoptext
>
> fails with the message:
> ! Undefined control sequence.
> <argument> \dosinglenarrower
>
> \redorepeatwithcommand [#1]#2->#2
> {#1}
> \dodorepeatwithcommand ...repeatwithcommand [#1]#5
> \else
> \dododorepeatwithcom...
>
> \next1 #1,->\docommand {#1}
> \doprocesscommaitem
> <argument> \relax left,
> right
> \doprocesscommalist ...aitem \gobbleoneargument #1
> ,]\relax \global
> \advance ...
> ...
> l.14 \startextract
>
>
> If I comment out \startnarrower[left,right] and \stopnarrower in the
> definition of \definestartstop[extract], the text is set (though not
> as I should like).
>
> Any suggestions?
>
Hi Alan,
simply download the current stable version (where \dosinglenarrower is
defined again).
Greetings, Peter
> Alan
>
>
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2006-11-21 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 21:04 Alan Bowen
2006-11-21 21:26 ` Peter Rolf [this message]
2006-11-22 12:51 ` Alan Bowen
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=45636F10.1010203@gmx.net \
--to=indiego@gmx.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).