From: jbf <roma83537@gmail.com>
To: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: reduced space below chapter title
Date: Wed, 3 Jun 2020 09:21:12 +1000 [thread overview]
Message-ID: <91c898f0-8561-0730-e07f-d61c4b5182c7@gmail.com> (raw)
In-Reply-To: <e06eda77-620a-07a1-f25d-fa0d4ae177b8@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2028 bytes --]
Thanks Wolfgang. Clearly that fixes the problem. I also came up with
another solution which avoids the need to define a MyChapterCommand, by
first setting up the normal chapter as:
\setuphead
[chapter]
[header=empty,alternative=middle,style=bold,numbercommand=\groupedcommand{}{\blank[2cm]},after={\blank[3cm]}]
and then setting up a mychapter as:
\definehead[mychapter][chapter]
\setuphead[mychapter][header=empty,alternative=middle,style=bold,numbercommand=\groupedcommand{}{\blank[2cm]},after={\blank[.5cm]}]
That gives me the result I am after as well as maintaining the style of
the standard chapter head.
Julian
On 3/6/20 12:58 am, Wolfgang Schuster wrote:
> jbf schrieb am 02.06.2020 um 11:41:
>> Hi list,
>>
>> I am attempting to achieve, for every second chapter, to have only
>> one line of space between the chapter title and the text that follows.
>>
>> I looked at the following example in the wiki:
>>
>> \setuppapersize[A6][A6]
>> \setupbodyfont[8pt]
>> \def\MyChapterCommand#1#2%
>> {\vbox to 4cm\bgroup
>> {#1\hskip.75em #2}
>> \vss
>> \egroup}
>> \setuphead[chapter][header=nomarking, command=\MyChapterCommand]
>> \starttext
>> \chapter{test} \input tufte
>> \stoptext
>>
>> and presumed that I could adjust that to something like 1cm instead
>> of 4cm.
>>
>> The problem is that when I try to process the original example, I get
>> a fatal error at the line which reads \chapter{test} \input tufte.
>>
>> I'm not sure why that error, but that aside, would the
>> \def\MyChapterCommand approach suggested above be the right way to
>> achieve my purpose? In other words, I want the text that follows the
>> chapter title to follow immediately for specific chapters, rather
>> than the considerable vertical space that follows the default setup
>> for chapter titles.
>>
>> Julian
>
> Change
>
> \def\MyChapterCommand#1#2%
>
> to
>
> \unexpanded\def\MyChapterCommand#1#2%
>
> or
>
> \define[2]\MyChapterCommand
>
> Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 3174 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-06-02 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 9:41 jbf
2020-06-02 14:58 ` Wolfgang Schuster
2020-06-02 23:21 ` jbf [this message]
2020-06-03 4:23 ` Wolfgang Schuster
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=91c898f0-8561-0730-e07f-d61c4b5182c7@gmail.com \
--to=roma83537@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=wolfgang.schuster.lists@gmail.com \
/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).