9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: pmarin.mail@gmail.com (pmarin)
Subject: [9fans] plan9 ms .if h test
Date: Wed, 30 Mar 2011 19:31:18 +0200	[thread overview]
Message-ID: <AANLkTi=14e+cgg_-4bz5b2+GCiidi4yu4UUBYxpE5wdy@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimXed3=2P7zy7MQ2roJC62msk-TZs7J3YCwsDss@mail.gmail.com>

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 distinguish between troff
and nroff. To write a conditional matching troff alone, use ?.if !h
.if t?."

http://swtch.com/plan9port/man/man7/htmlroff.html

Cheers.
pmarin.


On Wed, Mar 30, 2011 at 7:12 PM, pmarin <pmarin.mail at gmail.com> wrote:
> Never mind: ".if c" is only using for built-ins.
>
> On Wed, Mar 30, 2011 at 6:55 PM, pmarin <pmarin.mail at gmail.com> 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 the same meaning:
>> '''\" ? h - cover sheet basic distribution length
>>
>> Both tmac.cs and tmac.mcs load tmac.s in their inicialization so
>> probably h ?only have sense when tmac.cs or tmac.mcs are used.
>>
>> I think that if you are only using the ms macros then h is not
>> important because is not defined.
>>
>> Cheers.
>> pmarin.
>>
>>
>>
>>
>> On Wed, Mar 30, 2011 at 4:21 PM, Rudolf Sykora <rudolf.sykora at gmail.com> wrote:
>>> 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 you have
>>> .ie h .ll \\n(LLu
>>> .el \{\
>>> ...
>>> ]
>>>
>>> Thank you very much!
>>> Ruda
>>>
>>>
>>
>



  reply	other threads:[~2011-03-30 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 14:21 Rudolf Sykora
2011-03-30 16:55 ` pmarin
2011-03-30 17:12   ` pmarin
2011-03-30 17:31     ` pmarin [this message]
2011-03-30 18:03       ` Rudolf Sykora

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=14e+cgg_-4bz5b2+GCiidi4yu4UUBYxpE5wdy@mail.gmail.com' \
    --to=pmarin.mail@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).