From: Denis Maier <maier.de@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setupcolumnsetlines does not work
Date: Sat, 17 Aug 2019 15:14:36 +0200 [thread overview]
Message-ID: <CAMXdeGGTNDx922gU6zqTFU2c7OmXaxN5FVt_hGdp+6xe=y7GkA@mail.gmail.com> (raw)
In-Reply-To: <CAMXdeGEdOOUv2ADFdQundzTDOAihs5fb_zxoPfTVVwEZn6Fmfw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1584 bytes --]
Ok, have tried it now. No change ...
Am Sa., 17. Aug. 2019 um 13:33 Uhr schrieb Denis Maier <maier.de@gmail.com>:
> Also, what about \setupcolumnsetlines[Two][2][1][9]?
>
> Denis Maier <maier.de@gmail.com> schrieb am Sa., 17. Aug. 2019, 13:32:
>
>> If I am remembering correctly, the documentation has \setupcolumnsetlines
>> before \starttext.
>>
>> Sytse Knypstra <sytse.knypstra@home.nl> schrieb am Sa., 17. Aug. 2019,
>> 12:59:
>>
>>> In an effort to balance columns in a columnset layout, I found that in
>>> the following minimal example this effect is not obtained.
>>> After commenting out the first three lines after \starttext the result
>>> is ok.
>>> I am wondering what I overlooked this time.
>>>
>>> \definecolumnset[Two][n=2]
>>> \starttext
>>> \startcolumnset[Two]
>>> \input knuth
>>> \stopcolumnset
>>> \page
>>> \setupcolumnsetlines[Two][1][1][9]
>>> \startcolumnset[Two]
>>> \input knuth
>>> \stopcolumnset
>>> \stoptext
>>>
>>> Thank you for your suggestions,
>>>
>>> Sytse Knypstra
>>>
>>> ___________________________________________________________________________________
>>> 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
>>>
>>> ___________________________________________________________________________________
>>>
>>
[-- Attachment #1.2: Type: text/html, Size: 3210 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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:[~2019-08-17 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 10:59 Sytse Knypstra
2019-08-17 11:32 ` Denis Maier
2019-08-17 11:33 ` Denis Maier
2019-08-17 13:14 ` Denis Maier [this message]
2019-08-17 13:50 ` Denis Maier
2019-08-17 14:24 ` Wolfgang Schuster
[not found] ` <CAMXdeGE++3DccdgFz_PKMdZE2kS6dM5BYqbUK3U3CNUE46c1PQ@mail.gmail.com>
2019-08-17 15:00 ` Wolfgang Schuster
[not found] ` <CAMXdeGFbc=U7NuMC0Aqj7uF+n5eKO728EoYvykxWbyekvViWkA@mail.gmail.com>
2019-08-17 16:07 ` Wolfgang Schuster
[not found] <mailman.865.1566054029.1208.ntg-context@ntg.nl>
2019-08-17 19:03 ` Sytse Knypstra
[not found] <mailman.874.1566068640.1208.ntg-context@ntg.nl>
2019-08-17 21:54 ` Sytse Knypstra
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='CAMXdeGGTNDx922gU6zqTFU2c7OmXaxN5FVt_hGdp+6xe=y7GkA@mail.gmail.com' \
--to=maier.de@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).