Re: @Break semi-bug

[Adrian Kubala]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've been trying to understand this requirement by looking through the
"expert" manual, but it's a lot to digest just to understand this simple
case, and I'm still conceptually in the dark. If "//" joins objects
vertically, why doesn't "@Break" introduce the "//" itself? What meaning does
an "&"---which as far as I can tell is the same as "|", although I couldn't
find where it's explained explicitly---have after a vertical break?
Regardless, why does it "suppress" the meaning of the @Break?

I ask because I'm trying to create a simple macro like so, and get more
confusing behaviour which seems to have similar causes:

def @Letter right @Body
{
@Doc @Text @Begin
@PP
#//
@Body
@End @Text
}
...
@Letter @Begin
address@hidden
Blah blah
@End @Letter

If you uncomment the "@PP", the body doesn't wrap properly. If you uncomment
the "//", it's fixed. Is there a simple rule for when "//" is required that
doesn't require me knowing the implementation of the doc macros?

Thanks,
- -Adrian

On Sunday 06 May 2001 08:03 pm, Valeriy E. Ushakov wrote:
> On Sun, May 06, 2001 at 23:43:50 +0400, Adrian Kubala wrote:
> > The following, for example, does not work, placing all the "poem"
> > lines together as if a new break style was never specified:
> >
> > @Display @Heading{ Poem }
> > clines @Break {
>
> You need a vertical gap before the clines paragraph:
>
>     @Display @Heading{ Poem }
>     // clines @Break {
>
> clines is somewaht particular about its context, e.g. this is broken
> in the same way your original example is:
>
>     @Display @Heading{ Poem }
>     // & clines @Break {
>
> SY, Uwe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE69hVwKMBIRgg494cRAhpPAKCzuJzUKAVrsXVcOPs94794kIOX3wCff2Mq
963S4vpCeeeDiYqqirFcYno=
=81K5
-----END PGP SIGNATURE-----