From: Cecil Westerhof <cldwesterhof@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Why does startlines not work in a function
Date: Fri, 26 Apr 2013 17:19:57 +0200 [thread overview]
Message-ID: <CAG-LmmCF54Ov3M4=kwa3jn7GjG8wwKPak=4ZnFJxAMdBP6y5sA@mail.gmail.com> (raw)
I have the following code:
\startlines
\startalignment[center]
\setupindenting[no]
\doifelse {\getvariable{meta}{personalInfo}} {long} {
longline 1
longline 2
longline 3
longline 4
longline 5
longline 6
longline 7
longline 8
} {
shortline 1
shortline 2
shortline 3
shortline 4
}
\stopalignment
\stoplines
I wanted to put this in a function. So I wrote:
\def\Foo{
\startlines
\startalignment[center]
\setupindenting[no]
\doifelse {\getvariable{meta}{personalInfo}} {long} {
longline 1
longline 2
longline 3
longline 4
longline 5
longline 6
longline 7
longline 8
} {
shortline 1
shortline 2
shortline 3
shortline 4
}
\stopalignment
\stoplines
}
But then the text becomes one line instead of several lines.
So I had to rewrite it to:
\def\FooTwo{
\startalignment[center]
\setupindenting[no]
\doifelse {\getvariable{meta}{personalInfo}} {long} {
longline 1
longline 2
longline 3
longline 4
longline 5
longline 6
longline 7
longline 8
} {
shortline 1
shortline 2
shortline 3
shortline 4
}
\stopalignment
}
I called it first Foo2, but that worked havoc on Foo.
--
Cecil Westerhof
___________________________________________________________________________________
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 reply other threads:[~2013-04-26 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 15:19 Cecil Westerhof [this message]
2013-04-26 16:21 ` Hans Hagen
2013-04-26 20:30 ` Cecil Westerhof
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='CAG-LmmCF54Ov3M4=kwa3jn7GjG8wwKPak=4ZnFJxAMdBP6y5sA@mail.gmail.com' \
--to=cldwesterhof@gmail.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).