From: Steffen Wolfrum <st.wolfrum@estfiles.de>
Subject: Re: Again: "hanging" for a lot of paragraphs?
Date: Fri, 20 Feb 2004 10:45:34 +0100 [thread overview]
Message-ID: <a06002000bc5b85ee6e6b@[62.134.79.0]> (raw)
"a secret feature" - great!
So, sometimes it really is worthwhile to ask the same question twice :o)
Thank you very much Hans
Steffen
By the way: Any news from the placefigure-cookery?
Hans Hagen <pragma@wxs.nl> wrote:
> At 21:55 18/02/2004, you wrote:
> >Hi friends,
> >
> >there are for sure more sophisticated and more urgent problems,
> >but my question to me is really a big problem.
> >
> >Isn't there anybody that knows a command or a work-around that could help?
>
> Hm, for some time there is a secret feature in cont-new.tex which i still
> have to finish:
>
> \starttext
>
> \start
> \setupparagraphintro[reset,first][\hangafter-2 \hangindent2em FIRST]
> \input ward \blank \input ward \blank
> \input ward \blank \input ward \blank
> \stop
>
> \page
>
> \start
> \setupparagraphintro[reset,next][\hangafter-2 \hangindent2em NEXT]
> \input ward \blank \input ward \blank
> \input ward \blank \input ward \blank
> \stop
>
> \page
>
> \start
> \setupparagraphintro[reset,each][\hangafter-2 \hangindent2em EACH]
> \input ward \blank \input ward \blank
> \input ward \blank \input ward \blank
> \stop
>
> \stoptext
>
> The next option only works when you have the following patch in
> cont-new.tex (Search for original):
>
> \def\dosetupparagraphintro[#1][#2]%
> {\processallactionsinset
> [#1]
> [ \v!reset=>\global\chardef\everyparagraphintro\zerocount
> \global\everyfirstparagraphintro\emptytoks
> \global\everynextparagraphintro \emptytoks,
> \v!eerste=>\global\chardef\everyparagraphintro\plusone
> \doglobal\appendtoks#2\to\everyfirstparagraphintro,
> \v!volgende=>\ifcase\everyparagraphintro\global\chardef\everyparagraphintro\plusone\fi
> \doglobal\appendtoks#2\to\everynextparagraphintro,
> \v!elk=>\ifcase\everyparagraphintro\global\chardef\everyparagraphintro\plustwo\fi
> \doglobal\appendtoks#2\to\everyfirstparagraphintro
> \doglobal\appendtoks#2\to\everynextparagraphintro]}
>
>
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2004-02-20 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 9:45 Steffen Wolfrum [this message]
2004-02-20 10:16 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2004-02-20 12:27 Steffen Wolfrum
2004-02-18 21:53 Steffen Wolfrum
2004-02-18 20:55 Steffen Wolfrum
2004-02-18 21:19 ` Patrick Gundlach
2004-02-19 17:10 ` 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='a06002000bc5b85ee6e6b@[62.134.79.0]' \
--to=st.wolfrum@estfiles.de \
--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).