From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Fw: Subsections (spoke too soon)
Date: Tue, 31 Aug 1999 09:46:21 +0200 [thread overview]
Message-ID: <37CB884D.A2B92E24@wxs.nl> (raw)
In-Reply-To: <3.0.5.32.19990830221613.00b42ca0@mail.northcoast.com>
David Arnold wrote:
> Looks like I spoke too soon when I claimed we had a good solution with the
> subhead set up below. Now I have some terrible line breaks and indenting
> problems that I did not have before. I checked, and if I eleiminate the
> subsection setup below, my problems go away.
Can you send me (and gilbert -) the complete setup you use? In your
example I see no \subsection, so I wonder what happens. Maybe some
forgotten brace or so.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~1999-08-31 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-30 7:42 Fw: Subsections 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 [this message]
1999-08-30 19:34 ` Fw: Subsections David Arnold
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=37CB884D.A2B92E24@wxs.nl \
--to=pragma@wxs.nl \
--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).