From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Unwanted whitespace for tables and enumerations after \inmargin headings
Date: Fri, 18 Apr 2014 20:11:08 -0400 [thread overview]
Message-ID: <5351BF1C.7000302@rik.users.panix.com> (raw)
In-Reply-To: <alpine.LNX.2.03.1404181735000.16312@hzvpu.rqh>
On 2014-04-18 17:36, Aditya Mahajan wrote:
> On Fri, 18 Apr 2014, Thangalin wrote:
>
>> Hi Rik,
>>
>> The example isn't quite as minimal as it could be... Here is a
>> simplified version demonstrating the problem:
>>
>> \setuplayout[backspace=4cm]
>>
>> \define[2]\MarginHead{\inmargin{#1 #2}}
>>
>> \setuphead[section][
>> alternative=text,
>> command=\MarginHead,
>> ]
>>
>> \defineitemgroup[itemz]
>> \setupitemgroup[itemz][each][joinedup]
>>
>> \startbuffer[Item]
>> \startitemz
>> \item Item
>> \item Item
>> \stopitemz
>> \stopbuffer
>>
>> \starttext
>> \section{No Whitespace}
>> No extra whitespace before items.
>> \getbuffer[Item]
>>
>> \section{Extra Whitespace}
>> \getbuffer[Item]
>> Unexpected extra whitespace before items.
>> \stoptext
>
> Here is one way to get rid of the extra white-space. I could not
> figure out a clean way of adding this signal to the setup.
>
> \setuplayout[backspace=6cm, leftmargin=5.5cm]
>
> \define[2]\MarginHead{\inmargin{#1 #2}}
>
> \setuphead[section]
> [
> command=\MarginHead,
> alternative=text,
> distance=\zeropoint,
> ]
>
> \unprotect
> \def\SIGNAL{\hskip\d_strc_itemgroups_signal}
> \protect
> \defineitemgroup[itemz]
> \setupitemgroup[itemz][each][joinedup]
>
> \startbuffer[Item]
> \startitemz
> \item Item
> \item Item
> \stopitemz
> \stopbuffer
>
> \starttext
> \section{No Whitespace}
> No extra whitespace before items.
> \getbuffer[Item]
>
> \section{Extra Whitespace} \SIGNAL
> \getbuffer[Item]
> Unexpected extra whitespace before items.
> \stoptext
Pretty ugly, but thank you for that, Aditya.
Is there a similar kludge for tabulate? (That was part of my original
problem, removed in the subsequent simplification of the example.)
--
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2014-04-19 0:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 23:19 Rik Kabel
2014-04-18 19:54 ` Thangalin
2014-04-18 21:36 ` Aditya Mahajan
2014-04-19 0:11 ` Rik Kabel [this message]
2014-04-19 8:55 ` Wolfgang Schuster
2014-04-19 9:07 ` Thangalin
2014-04-19 15:46 ` Rik
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=5351BF1C.7000302@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).