From: Rik Kabel <context@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: dorecurse problem
Date: Thu, 19 Jan 2017 22:34:34 -0500 [thread overview]
Message-ID: <ee501659-9a2f-b245-ba91-3bb17dc21098@rik.users.panix.com> (raw)
ConTeXters,
When \dorecurse is active in the following MWE, the lines of text are
overprinted. At least, this is the case for me, please confirm it for
yourself. When \dorecurse is disabled, the lines print as they should,
separately. Please tell me what I am doing wrong with this, if anything,
and how to fix it. (Running ConTeXt ver: 2017.01.17 17:37 MKIV beta
fmt: 2017.1.19 on Win10 x64. There are no errors in the log.)
\definelayer
[blocks]
[width=\textwidth,
height=\textheight]
\setupbackgrounds
[page]
[background=blocks]
\starttext
\dorecurse{1}{ % comment to clear error
\startstandardmakeup
\setlayerframed
[blocks]
[preset=lefttop,
frame=off,
align=right]{
\startlines
Line one on the left
Line two on the left
\stoplines
}
\setlayerframed
[blocks]
[preset=righttop,
frame=off,
align=flushright]{
\startlines
thgir eht no eno eniL
thgir eht no owt eniL
\stoplines
}
\stopstandardmakeup
} % comment to clear error
\stoptext
--
Rik
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2017-01-20 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 3:34 Rik Kabel [this message]
2017-01-20 5:46 ` Otared Kavian
2017-01-20 7:59 ` Aditya Mahajan
2017-01-20 9:08 ` Hans Hagen
2017-01-20 16:42 ` Otared Kavian
2017-01-20 17:00 ` Rik Kabel
2017-01-20 17:06 ` 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=ee501659-9a2f-b245-ba91-3bb17dc21098@rik.users.panix.com \
--to=context@rik.users.panix.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).