On Wed, Sep 04, 2013, Tadziu Hoffmann wrote:
>
> > Some years ago, I wrote about the annoyance of absolute .sp
> > requests, which do not, contrary to intuition and logic,
> > take the top of the page as their starting point but rather
> > the top of the page plus 1v. Classic example:
> >
> > .v
> Some years ago, I wrote about the annoyance of absolute .sp
> requests, which do not, contrary to intuition and logic,
> take the top of the page as their starting point but rather
> the top of the page plus 1v. Classic example:
>
> .vs 12p
> .sp |6P
> foo
>
> "foo" is printed 6 picas plus a
On Tue, Sep 03, 2013, Ulrich Lauther wrote:
> why have I to use ADD_SPACE instead of SP just because I am at the
> top of the page?
> Seems to me an unneeded complication. Is there a deeper reason to
> make SP disfunctional after an *explicit* page break?
The only way to disable no-space mode aft
On Tue, Sep 03, 2013 at 01:40:31PM -0400, Peter Schaffter wrote:
> On Tue, Aug 27, 2013, Ulrich Lauther wrote:
> > However, when the user explicitely requests a new page, this seems
> > not to be needed: he/she knows that following text goes to a new page
> > and should be free to position it where
On Mon, Aug 26, 2013, Tadziu Hoffmann wrote:
>
> > > The problem you see is related to header traps. [...] and
> > > this behaviour is not controllable by `rs'. It seems that
> > > after the top header trap mom plants other, probably unused
> > > vertical traps.
>
> > Any suggestion for a clea
On Tue, Aug 27, 2013, Tadziu Hoffmann wrote:
> Otherwise, how would you do it? Well, the section macro could
> perhaps query register "nl" (vertical position of last printed
> text base-line), but that may be a bit chancy (depending on,
> for example, whether you output or not a page header on tha
> BTW, I never understood why the formatting macro packages
> don't like the user to put space at the top of their pages.
It's not about not wanting the user to put space at the top
if the user wants it, but rather about not putting space
there if it's not wanted.
Example: usually you want secti
> > The problem you see is related to header traps. [...] and
> > this behaviour is not controllable by `rs'. It seems that
> > after the top header trap mom plants other, probably unused
> > vertical traps.
> Any suggestion for a clean solution?
How about this:
.MAC MyNewPage END
.NEWPA
On Mon, Aug 26, 2013 at 12:41:53PM -0400, Peter Schaffter wrote:
>
> I don't know how ms handles this, but with mom, use the ADD_SPACE
> macro after NEWPAGE.
>
> .NEWPAGE
> .ADD_SPACE 5v
> text2
>
> ADD_SPACE exists precisely to solve the problem you're encountering.
> It's documented in section
On Mon, Aug 26, 2013, Ulrich Lauther wrote:
> I cannot reproduce the problem with plain groff, but came across it when
> using macro packages like mm or mom.
>
> This demonstrates the problem:
>
> .PRINTSTYLE TYPESET
> .HEADER_LEFT "top"
> .START
> text1
> .NEWPAGE
> .br
> .rs
> .br
> .sp 5
> te
On Mon, Aug 26, 2013, Ulrich Lauther wrote:
> I cannot reproduce the problem with plain groff, but came across it when
> using macro packages like mm or mom.
>
> This demonstrates the problem:
>
> .PRINTSTYLE TYPESET
> .HEADER_LEFT "top"
> .START
> text1
> .NEWPAGE
> .br
> .rs
> .br
> .sp 5
> te
On Mon, Aug 26, 2013, Werner Lemberg wrote:
> It seems that after the top header trap mom plants other, probably
> unused vertical traps. If you explicitly disable them with the
> .vpt command (see below), `rs' works just fine.
Which, with a few refinements, is what the ADD_SPACE macro does.
See
> I cannot reproduce the problem with plain groff, but came across it
> when using macro packages like mm or mom.
>
> This demonstrates the problem:
>
> .PRINTSTYLE TYPESET
> .HEADER_LEFT "top"
> .START
> text1
> .NEWPAGE
> .br
> .rs
> .br
> .sp 5
> text2
> .NEWPAGE
> text3
> .NEWPAGE
> foo
> .
On Mon, Aug 26, 2013 at 01:21:34AM +0200, Werner LEMBERG wrote:
>
> >> The groff manual says:
> >>
> >> .rs Restore spacing; turn no-space mode off.
> >>
> >> However,
> >> .rs
> >> .sp 3
> >> does not work; one has to output some text first, to get .sp to
> >> work.
>
> I don't under
>> The groff manual says:
>>
>> .rs Restore spacing; turn no-space mode off.
>>
>> However,
>> .rs
>> .sp 3
>> does not work; one has to output some text first, to get .sp to
>> work.
I don't understand the problem. Can you please give a complete
example which I can directly compile
On 25/08/13 20:55, Ulrich Lauther wrote:
>>> About the .nop request:
>>>
>>> .nop anything
>>> Always process anything.
>>>
>>> What is this request good for?
>>
>> It's good for things like
>>
>>.rs
>>.nop \&
>>.sp 3
>>
>> which is offers a solution to the .r
On Sun, Aug 25, 2013 at 02:00:08PM -0400, Peter Schaffter wrote:
> >
> > Is this a bug in groff, or in its documentation?
>
> I wonder about that, too. The info manual says very clearly
>
> "This mode [.ns] ends when actual text is output or the `rs'
> request is encountered..."
>
> Logica
On Sat, Aug 24, 2013, Ulrich Lauther wrote:
> The groff manual says:
>
> .rs Restore spacing; turn no-space mode off.
>
> However,
> .rs
> .sp 3
> does not work; one has to output some text first, to get .sp to work.
>
> Is this a bug in groff, or in its documentation?
I wonder about
The groff manual says:
.rs Restore spacing; turn no-space mode off.
However,
.rs
.sp 3
does not work; one has to output some text first, to get .sp to work.
Is this a bug in groff, or in its documentation?
What is the rationale for this behaviour?
About the .nop request:
.nop anyth
19 matches
Mail list logo
