|
From: | Jason Hoogland |
Subject: | Re: Lout-users Digest, Vol 48, Issue 5 |
Date: | Wed, 27 Jan 2016 15:37:57 +0800 |
Send Lout-users mailing list submissions to
address@hidden
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.nongnu.org/mailman/listinfo/lout-users
or, via email, send a message with subject or body 'help' to
address@hidden
You can reach the person managing the list at
address@hidden
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Lout-users digest..."
Today's Topics:
1. no @SectionList galley target (Jason Hoogland)
2. Re: no @SectionList galley target (Jeff Kingston)
----------------------------------------------------------------------
Message: 1
Date: Sun, 24 Jan 2016 11:17:24 +0800
From: Jason Hoogland <address@hidden>
To: address@hidden
Subject: no @SectionList galley target
Message-ID:
<address@hidden>
Content-Type: text/plain; charset="utf-8"
First post, absolutely love Lout, which I had written my PhD in it instead
of LaTeX.
Why do I get this error:
lout test.lout > test.ps
lout file "test.lout":
5,1: no @SectionList galley target precedes this
@SectionList&&preceding
for this test.lout input:
@SysInclude { report }
@Report
//
@Section
@Title { Heading A
}
@Begin
@PP
Some section
text
@BeginSubSections
@SubSection
@Title { Heading B
}
@Begin
@PP
Some section B
text
@End
@SubSection
@EndSubSections
@End @Section
p.s. completely tangential, but I can't believe a gnu mailing list sends me
my password in plain text in an email upon subscription, absolutely
infuriating!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nongnu.org/archive/html/lout-users/attachments/20160124/61e352a1/attachment.html>
------------------------------
Message: 2
Date: Sun, 24 Jan 2016 14:39:40 +1100
From: Jeff Kingston <address@hidden>
To: address@hidden
Subject: Re: no @SectionList galley target
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii
Jason,
I just tried your file, and it worked for me.
Try deleting file lout.li and running again. Sometimes if
you run Lout with structural errors in the input, traces of
them persist on subsequent runs. If you delete file lout.li
you get a fresh start.
Let us know how it goes.
Jeff
------------------------------
_______________________________________________
Lout-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lout-users
End of Lout-users Digest, Vol 48, Issue 5
*****************************************
[Prev in Thread] | Current Thread | [Next in Thread] |