Re: [groff] vertical resolution and page location traps

2018-06-17 Thread Ralph Corderoy
Hi, > > > > Reason is that traps are not recursive, IIRC: Traps are not > > > > handled while another trap is active (this seems to be missing > > > > in the info file). ... > > > > In other words, while your first trap is active, it moves down > > > > one line, which passes some traps without tri

Re: [groff] vertical resolution and page location traps

2018-06-16 Thread Werner LEMBERG
>> > Reason is that traps are not recursive, IIRC: Traps are not >> > handled while another trap is active (this seems to be missing in >> > the info file). > > But they are handled sequentially when a `.sp' passes more than one in a > single bound. Yes. >> > In other words, while your first tr

Re: [groff] vertical resolution and page location traps

2018-06-16 Thread Ralph Corderoy
Hi Dave, > Werner wrote: > > Reason is that traps are not recursive, IIRC: Traps are not handled > > while another trap is active (this seems to be missing in the info > > file). But they are handled sequentially when a `.sp' passes more than one in a single bound. $ cat two.tr .de trap1

Re: [groff] vertical resolution and page location traps

2018-06-15 Thread Dave Kemper
Thanks, Werner and Tadziu, for the prompt replies! That clears a few things up. Yes, I had read the Measurements section of the manual, but that's part of what confused me about the .V register. Where that section said "This basic unit, represented by a 'u', is a device dependent measurement," I

Re: [groff] vertical resolution and page location traps

2018-06-15 Thread Tadziu Hoffmann
> > The actual numbers returned under various conditions add only more > > confusion. > > > > $ groff -Tascii <<< '.tm \n(.V' > /dev/null > > 40 > > $ groff -Tps <<< '.tm \n(.V' > /dev/null > > 1 > > $ groff -Tpdf <<< '.tm \n(.V' > /dev/null > > 1 > > > > I don't see how the vertical resolution

Re: [groff] vertical resolution and page location traps

2018-06-15 Thread Werner LEMBERG
>> The actual numbers returned under various conditions add only more >> confusion. >> >> $ groff -Tascii <<< '.tm \n(.V' > /dev/null >> 40 >> $ groff -Tps <<< '.tm \n(.V' > /dev/null >> 1 >> $ groff -Tpdf <<< '.tm \n(.V' > /dev/null >> 1 >> >> I don't see how the vertical resolution of the asc

Re: [groff] vertical resolution and page location traps

2018-06-15 Thread Werner LEMBERG
> I'm having trouble understanding the .V register and how it > interacts with page location traps. > > The info manual's sole phrase describing this register is "Vertical > resolution in basic units." This is less than illuminating because > it doesn't address: basic units per what? A resolut

[groff] vertical resolution and page location traps

2018-06-15 Thread Dave Kemper
I'm having trouble understanding the .V register and how it interacts with page location traps. The info manual's sole phrase describing this register is "Vertical resolution in basic units." This is less than illuminating because it doesn't address: basic units per what? A resolution should