ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Possible bug with new \start ... \stop way for title, chapter, subject, etc.?
Date: Sat, 29 Jun 2013 18:10:23 +0200	[thread overview]
Message-ID: <E9243236-84A4-4E56-904F-865AEB69300C@gmail.com> (raw)
In-Reply-To: <CAGhDZhDP7uYUDPFxVOa0fXHe+TWbzk4FJcVpNf=m6Y+GvgWqaA@mail.gmail.com>


Am 29.06.2013 um 07:46 schrieb Andres Conrado Montoya <andresconrado@gmail.com>:

> I was trying to implement the solution provided by this thread:
> http://www.mail-archive.com/ntg-context@ntg.nl/msg51152.html and it
> works very well. However, finding a problem related to this
> implementation, I found that the output of the new \start ... \stop
> versions of the title, section, chapter, subject, etc. commands is
> different from the old \title, \chapter, \subject, etc.
> As you can see in the following MWE, the new implementation indents
> the first paragraph of the given section, by some amount (even
> different from the default for paragraphs).
> 
> Is this a bug or a new feature that I don't understand?

It’s a sometimes unwanted side effect of arguments for commands.
Even though there are ways to avoid the space you can’t add them
because there are cases where you want the space.

Below is a modified version of the older code which uses the new MkIV
mechanism to create customized head layouts which gobbles also
the space for \startsection.

\defineheadalternative
  [head:inleftmargin]
  [alternative=horizontal,
   renderingsetup=head:inleftmargin]

\startsetups[head:inleftmargin]
  \inleftmargin{\headtextcontent}
\stopsetups

\setuphead
  [section]
  [alternative=head:inleftmargin,
   style=bold,
   color=red,
   insidesection=\ignorespaces,
   distance=0pt]

\showframe

\starttext

\section{Knuth}
\input knuth

\startsection[title={Tufte}]
\input knuth
\stopsection

\stoptext

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


      parent reply	other threads:[~2013-06-29 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-29  5:46 Andres Conrado Montoya
2013-06-29 10:38 ` Pablo Rodríguez
2013-06-29 16:10 ` Wolfgang Schuster [this message]

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=E9243236-84A4-4E56-904F-865AEB69300C@gmail.com \
    --to=schuster.wolfgang@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).