ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: David Arnold <darnold@northcoast.com>
Subject: Re: Fw: Subsections
Date: Mon, 30 Aug 1999 12:34:19 -0700	[thread overview]
Message-ID: <3.0.5.32.19990830123419.00a53100@mail.northcoast.com> (raw)
In-Reply-To: <004001bef2bb$28ebc9e0$0c01a8c1@loginbv.com>

All,

Gilbert's solution worked perfectly. Thanks.

At 09:42 AM 8/30/99 +0200, you wrote:
>Sorry, something went wrong with my mailer (accidently sent the message too
>early).
>
>
>>
>> I would like to change the format of subsections. If I name a subsection
>with
>>
>> \subsection{Troubleshooting Function M-files}
>>
>> then I would like the following formats.
>>
>> A little bit of blank space before the subsection, but not so much as
>there
>> is now. The title of the subsection (without a number preceding),
>flushleft
>> to the margin, in the same font size as the regular body font, but bold,
>> with a period after the subsection title, then run-in to the remainder of
>> the text, as in
>
>Nice challenge, but in the end pretty easy:
>
>\setuphead
>  [subsection]
>  [alternative=text,
>   before={\blank[10pt]},
>   after=,
>   style=bold,
>   command=\mysubsection]
>
>
>\def\mysubsection#1#2{#2.}
>
>You could also say: number=no, to tell context, that this will not be
>numbered. Though the output is not an different at all, the table of
>contents would be. EXperimenting is the game here.
>
>
>Now I wonder, would Hans come up with a completely different solution?
>
>Gilbert.
>
>
>


      parent reply	other threads:[~1999-08-30 19:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-30  7:42 Gilbert van den Dobbelsteen
1999-08-30  9:01 ` Hans Hagen
1999-08-31  5:16   ` Fw: Subsections (spoke too soon) David Arnold
1999-08-31  7:46     ` Hans Hagen
1999-08-30 19:34 ` David Arnold [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=3.0.5.32.19990830123419.00a53100@mail.northcoast.com \
    --to=darnold@northcoast.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).