ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Henning Hraban Ramm <texml@fiee.net>
Subject: Re: additional space with sidebar and narrower
Date: Sun, 7 Apr 2019 21:32:30 +0200	[thread overview]
Message-ID: <d91014a6-e470-3888-f29c-dc52d0c6156f@xs4all.nl> (raw)
In-Reply-To: <FDE27284-EA50-4FBE-A4E2-63C30052E6DB@fiee.net>

On 4/7/2019 8:44 PM, Henning Hraban Ramm wrote:
> Am 2019-03-27 um 00:06 schrieb Henning Hraban Ramm <texml@fiee.net>:
> 
>> Am 2019-03-26 um 17:22 schrieb Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>:
>>
>>> Henning Hraban Ramm schrieb am 26.03.19 um 16:04:
>>>> Thank you, I found that myself (could have written).
>>>>
>>>> But the problem is that there’s space introduced if I use both environments, but not if I use only one. And I didn’t find how I can avoid that.
>>> Change the order of both environment and put sidebar in the narrower block.
>>>
>>> The reason for the extra line is that \startsidebar begins a new paragraph but \startnarrower end the lest paragraph which results in a single empty line.
>>
>> Thank you, that works in my MWE, but not in my real life book. (I was sure I tested that approach already...) I’ll investigate further.
> 
> I finally found out what’s the problem:
> 
> \starttext
> 
> \input tufte
> 
> \startnarrower
> \startsidebar
> \startparagraph
> \input knuth
> \stopparagraph
> \stopsidebar
> \stopnarrower
> 
> \input tufte
> 
> \stoptext
> 
> As soon as I use \start/stopparagraph within narrower and sidebar, there’s additional space introduced. How can I avoid that?
swap 'm

\startnarrower
\startparagraph
\startsidebar
\input knuth
\stopsidebar
\stopparagraph
\stopnarrower

-----------------------------------------------------------------
                                           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
___________________________________________________________________________________

  reply	other threads:[~2019-04-07 19:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26 10:16 Henning Hraban Ramm
2019-03-26 14:22 ` Otared Kavian
2019-03-26 15:04   ` Henning Hraban Ramm
2019-03-26 16:22     ` Wolfgang Schuster
2019-03-26 23:06       ` Henning Hraban Ramm
2019-04-07 18:44         ` Henning Hraban Ramm
2019-04-07 19:32           ` Hans Hagen [this message]
2019-04-08  5:59             ` Henning Hraban Ramm

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=d91014a6-e470-3888-f29c-dc52d0c6156f@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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).