From: "Gilbert van den Dobbelsteen" <gilbert@login-bv.com>
Subject: Re: Subsections
Date: Mon, 30 Aug 1999 09:22:56 +0200 [thread overview]
Message-ID: <002a01bef2b8$7b40c860$0c01a8c1@loginbv.com> (raw)
In-Reply-To: <3.0.5.32.19990829141119.00b30430@mail.northcoast.com>
>
> 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:
\setupsection
[subsection]
[
]
next prev parent reply other threads:[~1999-08-30 7:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-29 21:11 Subsections David Arnold
1999-08-30 7:22 ` Gilbert van den Dobbelsteen [this message]
1999-08-30 7:30 ` Subsections Tobias Burnus
1999-08-30 8:23 ` Subsections Tobias Burnus
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='002a01bef2b8$7b40c860$0c01a8c1@loginbv.com' \
--to=gilbert@login-bv.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).