space before lists

Hi,

How do I remove the red vertical space? (image attached)

My table code is:

 <at> LP  <at> Tbl
width { expand }
rule { yes }
aformat {
 <at> Cell indentvertical {ctr} indent { ctr }  <at> B clines  <at> Break A |
 <at> Cell width {1c} indent { ctr } indentvertical {foot} 90d  <at> Rotate  <at> B B |
 <at> Cell width {1c} indent { ctr } indentvertical {foot} 90d  <at> Rotate  <at> B C |
 <at> Cell indentvertical {ctr} indent { ctr }  <at> B clines  <at> Break D |
 <at> Cell width {1.5i} indentvertical {ctr} indent { ctr }  <at> B clines  <at> Break E }
bformat {  <at> Cell A |  <at> Cell width {1c} B |  <at> Cell width {1c} C |  <at> Cell D |  <at> Cell width {1.5i} E }
{
 <at> Rowa
A { Componente del Proyecto }
B { Estudiante }
C { Profesor }
D { Recursos Disponibles }
E { Notas }

 <at> Rowb
A { Hacer nuevas carpetas }
D {
 <at> BulletList
 <at> ListItem { Cartilla Organizando Carpetas }
 <at> EndList

<at> BookSetup chapters - how to prevent chapter title page?

Experiences with Lout

Hi,

in the following I would like to share my experiences with Lout from the
last six months. I'm writing my PhD thesis and started with LaTeX. I want
a rather 'stylish' thesis with nice headers, customized fonts and framed
and colored content. After I wasted hours searching the net, digging into
the source, adding several hacks, fighting with version incompatibilities 
-- I was still not able to achieve my design. Two simple examples, I
failed to achieve: opening chapters on the left side always (without
using the Memoir or Koma class) and use the same header 'style' in
Index and Bibliography, as with the rest of the document. To be
honest: I think LaTeX is a mess and a large Hack: the Memoir class here 
on my installation has 12750 lines... 

I'm fan of suckless software (e.g. using dwm/dmenu on a daily basis) and
I like the KISS principle, so I gave up on LaTeX and started looking for
alternatives and stumbled over Lout. I was surprised about the simplicity,
the speed and concepts. I was able to implement my whole thesis design
with fancy colors, frames, custom headings, ... in less than 16h (thanks
to the awesome user guide). On top, I finally got rid of Gnuplot all the
other crappy and bloated software for graphics and diagrams (hey, Gnuplot
still can not handle pie graphs... ).

To summarize: I'm convinced, Lout is great and saved me several hours of 
time. Thank you very much for writing this amazing piece of software!

Nevertheless now, to the drawbacks :)
While writing the thesis with Lout 3.39 (on OpenBSD), I stumbled over
several things, I would like to share here, please see below. Maybe you
can comment on some of these.

Thanks,
Regards,
Joerg

Minor Issues:
-  <at> DP and the Option  <at> DisplayGap are really 'overloaded' and used in too many 
  places.  <at> DP should especially not used be between captions and 
  Figures/Table/Floaters. I think this was already mentioned somewhere in the
  mailing lists archive.
- When setting  <at> ChapterStartPages { Even } and using the colophon, the
  colophon seems to be broken.
-  <at> Place does not work from heading definitions in book template 
  (not yet defined/wrong context): Workaround: copy&paste own  <at> Place into 
  included 'mydefs'.
-  <at> Place + Landscape does not do what (I) expected (things are kept instead
  of rotated). I guess this is because,  <at> Place is a Lout primitive
  operating on a lower (Postscript) level? This should at least be
  documented or mentioned somewhere.
- Defintion/Claim/Example/Proposition TitleFormat seems not to be used (with 
  book).
- Graph dashlength option(s) seem to be ignored (nothing visible happens).
- Diag link pathwidth set to thick + shadowbox + paint will result in links
  crossing inside into the boxes. Suggested fix: move the Links 'below' the
  boxes or do really end on the box border.
-  <at> Python misses """ comments """, a short look into the code suggests, that 
  this is probably simple to fix. 
- Overheads:  <at> Lectures  <at> RunningTitle seems to be ignored 
- Overheads: with  <at> Lectures the default  <at> OverheadNumInDisplays { No } seems
  not to be applied.  

Sane Defaults:
- Abbreviations Chapter should really be part of Introduction (resulting in
  Roman Numbers instead of Arabic with the default settings).
- Captions in Figure/Table/Floater are not left justify-able as centered with 
  |0.5rt| by default. Workaround:  <at> FigureCaptionFormat {  <at> HExpand ...
- Overheads: Content/References title should not be centered by default,
  this makes it impossible to have a Left-Aligned Layout. Workaround:
  ContentWord {  <at> HExpand Outline })
- Overheads: I think A4 portrait as default is not very useful. Something
  like B5 or letter combined with landscape is way better for beamer
  presentations.

Documentation:
- User Guide: orragged vs outdent example -- no visible difference in the 
  example?
- User Guide:  <at> Overheads,  <at> RunningTitle option as showed in Examples is useless,
  as ignored anyways.

Others/Feature (Requests):
- List of Figures, List of Tables, List of Floaters: an InContents { no }
  option is missing.
- With  <at> ChapterStartPages { Even } it would be nice to override this option,
  especially for Preface to avoid empty pages. Workaround: I moved content from
  preface to  <at> AfterTitlePage.
- There is no VERTICAL RULE, why??? I implemented my own based on some list
  archive suggestions:
  import  <at> BasicSetup
  def  <at> TVLine {  <at> TGray { "0 0 moveto 0 ysize lineto stroke"  <at> Graphic {} } }
- No abbreviation macros :( I ended up in implementing my own poor man macro:
  import  <at> BasicSetup
  def  <at> TAc right a { a  <at> CrossLink {  <at> S a } }
  And later using it like this:  <at> TAc AAD in the Text, with a List in the
  Appendix:
   <at> VeryWideTaggedList
   <at> TagItem {  <at> S AAD  <at> PageMark AAD } { Average Absolute Deviation }
   <at> EndList
- No (auto)  <at> Sym carriagereturn in listings on line breaks. Workaround:
  manually possible with Lout code in comments of listings.
- Shell/logfile and plain listing style is missing. Workaround: I re-used 
  Haskell.
- Colors: Specification in RGB Hex ala HTML/CSS would be nice. Workaround: 
  pre-calc or { bc -l }  <at> Pipe :)
-  <at> *NumberedDisplay number format: left side numbers are not possible :(
- Would be nice to have a Bibtex to Lout converter. I was to lazy to write
  one, but I guess with some Perl/String/Regex foo this is done in a short
  time and may motivate other users to switch to Lout :)
- I personally think the Plain and PDF export is useless and can be dropped.
  Both work only very limited and there are tools available to convert from PS
  to PDF to TXT and back.
-> For me ps2pdf works fine, once I figured out that
   I need to set some options correctly:
   ps2pdf -sFONTPATH=fonts/ -sPAPERSIZE=isob5 thesis.ps
-> IsoB5 vs Louts JisB5 -> Workaround: use customized 'other' page size in Lout.
- Diag Links really miss a color option. Workaround: colorize manually.
-  <at> Graph definitely misses an option to set fonts (workaround is set whole
  graph). Furthermore, why no 'copy and local include template' for inheritance
  of default options similar to book, tbl and diag, etc.?  
-  <at> Graph axes width is not configurable. Would be nice to have an axis
  line width option (for bigger axis than data lines). 
- A CrossLink to the line numbers of  <at> CP would be nice to have, to be able to
  reference listing lines in text.

Re: Equation with condition

Le Mon, 18 Mar 2013 11:23:01 -0400,
Pierre Lesimple <pierre.lesimple <at> mcgill.ca> a écrit :

> Le Mon, 18 Mar 2013 01:23:37 -0700,
> Daren Scot Wilson <darenw <at> darenscotwilson.com> a écrit :
> 
> > I've gone temporarily dense or something, not seeing this in the
> > User's Guide.  I know how to write an equation on a line of its own,
> > for example
> > 
> >       x = y
> > 
> > using
> >  <at> CenteredNumberedDisplay  <at> Tag {profound123}  <at> Math {x=y}
> > 
> > But how would I add a condition following the equation,  something
> > like
> > 
> >       x = y     for x>0
> > 
> > but of course looking good?
> > 
> 
> I would go for 2 columns (horizontal concatenation, two  <at> Math{}
> objects) in that particular case, but I don't know how the "flow" of
> equations would look like as a whole...
> 

As a precision,

 <at> CenteredNumberedDisplay  <at> Tag {profound123} { <at> Eq {x=y} |1c  for  <at> Eq
{x>0}} 
 <at> CenteredNumberedDisplay  <at> Tag {profound124}   <at> Eq {y=az+b}

seems to do what you want to do, if you don't mind the "centered" look
of it.

Equation with condition

I've gone temporarily dense or something, not seeing this in the User's 
Guide.  I know how to write an equation on a line of its own, for example

      x = y

using
 <at> CenteredNumberedDisplay  <at> Tag {profound123}  <at> Math {x=y}

But how would I add a condition following the equation,  something like

      x = y     for x>0

but of course looking good?

--

-- 
Daren Scot Wilson
Escondido California

About <at> Eq and double integral

Hi all,

How to get a beautiful double integral symbol ?

Here is what I've done :
 <at> Eq { big int big int sub Sigma f(x) dx }
but the result is not so pretty !

I'd like something like here : http://personal.maths.surrey.ac.uk/st/S.Gourley/double_int.pdf

Thanks

Dominique Cretel

fill/page justify in macros

<at> NP in macros

Additional formatting inside <at> CP

While we are on this topic...  I recently needed to highlight bits of
code inside  <at> CP without manual editing of prg2lout output and without
additional filtering (corporate laptop with windows, so  <at> Filter is a
problem). 

I came up with the following quick hack that someone might also find
useful (or at least it's archived for my own future reference :).

 <at> CP  <at> Begin
...
      do_stuff();
/* <at>  <at> ShowBackground {  <at> ASTRUT# */
#ifdef SPECIAL
      do_special_stuff();
#endif/* <at> #
 <at> ZSTRUT}*/
      do_more_stuff();
...
 <at> End  <at> CP

Where

macro  <at> ASTRUT { 0.8w  <at> VShift 1f  <at> High {} //0io "" }
macro  <at> ZSTRUT { 0.3w  <at> VShift 1f  <at> High {} }

and  <at> ShowBackground is bog standard  <at> Graphics to fill background:

def  <at> ShowBackground
  named  <at> BG { 0.90 }
  right x
{
  { 0 0 moveto xsize 0 lineto xsize ysize lineto 0 ysize lineto
    closepath  <at> BG setgray fill
  }  <at> Graphic x
}

The /* <at>  comments should be used *exactly* as shown, with embedded lout
comments (to deal with "lines"  <at> Break vs. leading whitespace) and the
closing /* <at>  comment split.

It's sort of nasty, but keeps the source code in the main document in
the form pretty close to original.

-uwe

How do you set <at> Book { <at> Title{} } font size?

Hi,

I have

     <at> Book
	 <at> Title{The Title}

but I can't see how to set the  <at> Title's font size (and using, say, 
	 <at> Title{27p  <at> Font{The Title}}
has no effect.

Thanks!

--

-- 
Mark Summerfield, Qtrac Ltd, www.qtrac.eu
    C++, Python, Qt, PyQt - training and consultancy
        "Programming in Python 3" - ISBN 0321680561
            http://www.qtrac.eu/py3book.html

prg2lout raw mode