9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] line numbers in troff
Date: Fri, 20 May 2011 00:51:11 +1000	[thread overview]
Message-ID: <BANLkTi=hJRgncbRnswTwTmgUY8UnuXOjiA@mail.gmail.com> (raw)
In-Reply-To: <59b7f7c11e04848db87971028f2813a1@plan9.cs.bell-labs.com>

.nm is your friend.

brucee

On Fri, May 20, 2011 at 12:43 AM, Sape Mullender
<sape@plan9.bell-labs.com> wrote:
> I think at the top of the page you set a trap to go off at the next line.
> In the trap macro you reset the trap for the line after that.  And so on,
> down the page.
>
>        Sape
>
>> Funny you should mention this. I know there is a way (done for patent
>> applications). I think I can find it in the troff doc. I have to by
>> tomorrow so I'll report back.
>>
>> brucee
>>
>> On Thu, May 19, 2011 at 11:44 PM, Steve Simon <steve@quintile.net> wrote:
>>> macros are easy enough: start them with .de XX and end them with .., e.g.
>>> start and end code example which I end up adding to most documents I write:
>>>
>>> .de EX
>>> .nj
>>> .nf
>>> .CW
>>> .SM
>>> ..
>>>
>>> .de EE
>>> .fi
>>> .ju
>>> .LG
>>> .R
>>> ..
>>>
>>> There are quite a few books, see http://www.troff.org/ , my favorite is
>>> "Document formatting & typsetting on the UNIX system".
>>>
>>> I really don't know how you would add line numbers, if you are lucky there
>>> may be a well-known macro which is run at the start of every line...
>>>
>>> -Steve
>>>
>>>
>
>
>



  reply	other threads:[~2011-05-19 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 13:09 hugo rivera
2011-05-19 13:44 ` Steve Simon
2011-05-19 14:38   ` Bruce Ellis
2011-05-19 14:43     ` Sape Mullender
2011-05-19 14:51       ` Bruce Ellis [this message]
2011-05-19 17:15 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-05-19 20:48 ` Charles Forsyth
2011-06-08  2:13   ` hugo rivera

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='BANLkTi=hJRgncbRnswTwTmgUY8UnuXOjiA@mail.gmail.com' \
    --to=bruce.ellis@gmail.com \
    --cc=9fans@9fans.net \
    /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).