ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik Kabel <context@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Unwanted whitespace with \startsection and in-margin headings
Date: Thu, 17 Apr 2014 23:37:38 -0400	[thread overview]
Message-ID: <53509E02.3000806@rik.users.panix.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1598 bytes --]

Following up on a related whitespace problem with descriptions and 
tables following in-margin headings --

I notice that \startsection behaves differently from \section when it 
comes to following whitespace for in-margin headings. This example 
demonstrates this:

    \setuplayout [backspace=6cm,leftmargin=6cm,rightmargin=1cm,cutspace=1cm]

    \setuphead   [chapter][page=no]
    \setuphead   [section][distance=0pt,
                   alternative=text,
                   command=\MarginHead]

    \define[2]\MarginHead{\inmargin{#1 #2}}

    \starttext

    \chapter{Traditional}

    There is no extra white space when using the traditional
    sectioning commands when the heading is placed in the margin.

    \section{No blank line}
    This text follows the section heading with no intervening space.
    No extra space has been added.

    \section{Blank line}

    This text follows the section heading with one intervening blank
    line. No extra space has been added.

    \startchapter[title={Startsection}]

    The newer sectioning commands are sensitive to the whitespace which
    follows when the heading is placed in the margin.

    \startsection[title={No blank line}]
    This text follows the section heading with no intervening space.
    No extra space has been added.

    \stopsection
    \startsection[title={Blank line ?}]

    This text follows the section heading with one intervening blank
    line. It shows the problem with startsection.

    \stopsection
    \stopchapter
    \stoptext

What can be done with the header setup to prevent this?

-- 
Rik Kabel

[-- Attachment #1.2: Type: text/html, Size: 3027 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

                 reply	other threads:[~2014-04-18  3:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=53509E02.3000806@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).