From: Thomas Floeren <thfl@mac.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Columns and clubpenalty problem
Date: Fri, 28 Feb 2014 19:17:29 +0100 [thread overview]
Message-ID: <4B098DCD-33EA-47AA-B948-2C8DB1457599@mac.com> (raw)
In-Reply-To: <00E544FC-6ABA-419B-8CBA-5555F17C05AA@me.com>
> Hi all,
>
> I've the same problem, w/o solution.
> An alternative is a double line brake, but it's not a durable solution…
>
> Pierre Bovet
>
> Le 4 févr. 2014 à 14:52, Thomas Floeren <thfl@mac.com> a écrit :
>
Sorry for bumping, but the bug is still there in the current Beta (2014.02.14 17:07).
Or, is it not a bug, and I’m doing something wrong?
In that case any hint is appreciated.
Thank you
--
Thomas
On 17.02.2014, at 15:48, Pierre Bovet <pierre67@me.com> wrote:
> Hi all,
>
> I've the same problem, w/o solution.
> An alternative is a double line brake, but it's not a durable solution…
>
> Pierre Bovet
>
> Le 4 févr. 2014 à 14:52, Thomas Floeren <thfl@mac.com> a écrit :
>
>> Hi,
>>
>> with the recent Betas, and the Current, I have a problem with columns and
>> clubpenalty. In the following minimal the long item (item 1) will introduce
>> a column break (instead of a simple line break):
>>
>> \def \defaultclubpenalty{\plustenthousand}
>>
>> \starttext
>> \startitemize [columns]
>> \item This is just a long line and should stay in the left column.
>> \dorecurse{10}{\item bla bla bla}
>> \stopitemize
>> \stoptext
>>
>> Older ConTeXt versions work as expected (no column break in item 1), for example
>> Beta 2013.11.13 12:28 or Current 2013.05.28 00:36.
>>
>>
>> Thomas Floeren
>>
>> ___________________________________________________________________________________
>> 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
>> ___________________________________________________________________________________
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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 prev parent reply other threads:[~2014-02-28 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 13:52 Thomas Floeren
2014-02-17 14:48 ` Pierre Bovet
2014-02-28 18:17 ` Thomas Floeren [this message]
2014-03-07 12:38 ` Thomas Floeren
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=4B098DCD-33EA-47AA-B948-2C8DB1457599@mac.com \
--to=thfl@mac.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).