> I've finally worked up what I hope is a good patch (it's been a
> while since I've generated one, so let me know if this is broken
> somehow). It's at the bottom of this message.
Thanks! Will incorporate as soon as I have some time.
>> No-space mode is fully documented in the info pages of g
On Sat, Jul 16, 2011 at 12:39 AM, Werner LEMBERG wrote:
>> meintro.me doesn't document .bl at all, talking only about .sp as a
>> way to leave vertical space (in section 2.4). This would be a good
>> place to add text [...]
>
> I would be glad if you could provide patches for groff_me.man and
> m
> meintro.me doesn't document .bl at all, talking only about .sp as a
> way to leave vertical space (in section 2.4). This would be a good
> place to add text [...]
I would be glad if you could provide patches for groff_me.man and
meref.me, and, if necessary, for meintro.me also.
>
>.bl
>> So it looks like -me and -ms break the .sp request in this context.
>
> Well "break" is probably not the right word, since it implies
> that this behavior is "not correct", whereas the behavior is
> actually intended.
You're right; I shouldn't have used the word "break" especially for
macro pac
Tadziu and Werner -- thank you for the clarifica-
tion.
Anton
I said:
> Ted Harding suggested that I use the zero-width
> character...
It was Ralph Corderoy. Sorry.
Anton
> I think that the vertical position is initialized to -1 before any
> text has been output is also by design, to be able to set page
> margins on the first page with a ".wh 0 xx" trap. To quote the
> Troff User's Manual:
>
> A pseudo-page transition onto the first page occurs either when
> t
> So it looks like -me and -ms break the .sp request in this context.
Well "break" is probably not the right word, since it implies
that this behavior is "not correct", whereas the behavior is
actually intended. The macro packages set up a top margin
and skip this margin when outputting text. A
Dave Kemper:
> I get different results with your sample code
> depending on which macro package I use. Putting
> your code in a file called "test" and running
> groff 1.21:
> [...]
Thank you for the test, Dave. I only tested this
with no package and with -mm, which also causes .
> The
> problem is caused by the vertial position registers
> (.d and nl) not being affected by the .sp request.
Anton,
I get different results with your sample code depending on which macro
package I use. Putting your code in a file called "test" and running
groff 1.21:
$ groff test > /dev/
Ralph Corderoy:
> To make the first .tm print 0 add a line at the
> beginning containing just
>
> \&
Hello, Ralph, and thanks.
In order to completely get rid of the side effect of
the invisible character I used:
\&
.br
.sp -1v \"Return to initial location
But why is GROFF behaving like
Hi Anton,
> .tm Initial vert. pos.: \n[.d]
> .sp 40u
> .tm Vert. pos. after .sp 40:\n[.d]
> .sp 40u
> .tm Vert. pos. after another .sp 40:\n[.d]
> Some text
> .sp 40u
> .tm Vert. pos. after .sp 40 after text: \n[.d]
>
> If this is the correct behavour, how to work
Hello again,
One of my macros does not work when called first in
the document, before any text has been output. The
problem is caused by the vertial position registers
(.d and nl) not being affected by the .sp request.
Here is an example:
.tm Initial vert. pos.: \n[.d]
.sp 4
13 matches
Mail list logo
