From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: dorecurse problem
Date: Fri, 20 Jan 2017 10:08:54 +0100 [thread overview]
Message-ID: <00e391b3-941e-95c3-7cbb-a6ce980b4bae@wxs.nl> (raw)
In-Reply-To: <alpine.OSX.2.02.1701192356450.5588@nqv-znpobbx>
On 1/20/2017 8:59 AM, Aditya Mahajan wrote:
> On Thu, 19 Jan 2017, Rik Kabel wrote:
>
>> 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.)
>
> This has nothing to do with \dorecurse, but due to the fact that the
> argument of \dorecurse or any macro is parsed before the catcode changes
> introduced by \startlines come into effect. Here is a simpler example
> demonstrating similar behavior:
>
> \def\test#1{#1}
>
> \starttext
> \test{Something
> \startlines
> Line one
> Line two
> \stoplines}
> \stoptext
>
> Depending on what you want to do, it should be possible to come up with
> a workaround.
\startbuffer
\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
\stopbuffer
\dorecurse{1}{
\getbuffer
}
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 prev parent reply other threads:[~2017-01-20 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 3:34 Rik Kabel
2017-01-20 5:46 ` Otared Kavian
2017-01-20 7:59 ` Aditya Mahajan
2017-01-20 9:08 ` Hans Hagen [this message]
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=00e391b3-941e-95c3-7cbb-a6ce980b4bae@wxs.nl \
--to=pragma@wxs.nl \
--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).