On 30 March 2011 19:31, pmarin wrote:
> To make it easier to write input files that can be formatted by both
> troff and htmlroff, htmlroff adds a new condition h which evaluates
> true in .if and .ie requests. The t condition continues to evaluate
> true, to accomodate input files trying to disti
I found it.
from htmlroff(1):
"Conditional input
To make it easier to write input files that can be formatted by both
troff and htmlroff, htmlroff adds a new condition h which evaluates
true in .if and .ie requests. The t condition continues to evaluate
true, to accomodate input files trying to
Never mind: ".if c" is only using for built-ins.
On Wed, Mar 30, 2011 at 6:55 PM, pmarin wrote:
> I searched where the register h is defined:
>
> % 9 grep -n '.nr h ' tmac.*
>
> tmac.cs:103: .nr h 6
> tmac.cs:477: . nr h \\ne \}
> tmac.mcs:208: .nr h 6
> tmac.mcs:840: .nr h \\ne
>
> where h has
I searched where the register h is defined:
% 9 grep -n '.nr h ' tmac.*
tmac.cs:103: .nr h 6
tmac.cs:477: . nr h \\ne \}
tmac.mcs:208: .nr h 6
tmac.mcs:840: .nr h \\ne
where h has the same meaning:
'''\" h - cover sheet basic distribution length
Both tmac.cs and tmac.mcs load tmac.s in their
Hello 9fans,
in the troff ms-definition file (in plan 9, p9p)
/sys/lib/tmac/tmac.s
I can find this structures
.if h ...
or
.ie h ...
I really can't find what this test means (the 'h'), I only know the
o,e,t,n built-ins.
Please, can anybody tell?
[
In p9p, it's e.g. on
/opt/plan9/tmac/tmac.s:329
