Can somebody tell me how this works please?
I am getting nowhere.
I called
.INITI
to initialize
.IND "keyword"
to save an entry and
.INDP
to print and I get 2 pages of emptiness.
Thanks - Damian
Pacific Engineering Systems International . 20D Grose St, Glebe
Hi Damian,
At 2023-06-30T17:47:43+1000, Damian McGuckin wrote:
> Can somebody tell me how this works please?
The groff_mm(7) page _as it is set to ship in groff 1.23.0_ might be
more helpful than its 1.22.4 incarnation. I did some work in this area
recently, even after 1.23.0.rc4.
Long story sh
Are any of the solutions put forth in this thread suitable for commit
to groff git (obviously not on master till it's unfrozen)? They don't
appear to have been pushed to any of the branches. And I don't see a
savannah ticket for the issue.
On Friday, 30 June 2023 15:43:49 BST Dave Kemper wrote:
> Are any of the solutions put forth in this thread suitable for commit
> to groff git (obviously not on master till it's unfrozen)? They don't
> appear to have been pushed to any of the branches. And I don't see a
> savannah ticket for the
Hi Branden,
On Fri, 30 Jun 2023, G. Branden Robinson wrote:
Does this help?
No. But maybe it is me.
.INITI P "damian" \" I must create "damian.ind" beforehand
.IND item0
.IND item1
.IND item2
.INDO \" at the point where I want the Index
I see a
Hi Deri,
At 2023-06-30T16:09:55+0100, Deri wrote:
> On Friday, 30 June 2023 15:43:49 BST Dave Kemper wrote:
> > Are any of the solutions put forth in this thread suitable for
> > commit to groff git (obviously not on master till it's unfrozen)?
> > They don't appear to have been pushed to any of t
Hi Damian,
Okay. Here is the example I used to figure out the feature and update
the documentation. This is using groff 1.22.4. You will notice page
breaks in annoying places (this is a bug fix I have queued for
post-1.23.0), but the index _is_ present.
Procedure:
$ mkdir /tmp/branden/damian
On Friday, 30 June 2023 16:26:51 BST G. Branden Robinson wrote:
> Hi Deri,
>
> At 2023-06-30T16:09:55+0100, Deri wrote:
> > On Friday, 30 June 2023 15:43:49 BST Dave Kemper wrote:
> > > Are any of the solutions put forth in this thread suitable for
> > > commit to groff git (obviously not on maste
Hi Branden,
I stayed up watching the cricket. It has now finished.
On Fri, 30 Jun 2023, G. Branden Robinson wrote:
Sorry, those were grep'ed frominside my own text but I was not using
'mmroff'. I thought I could use 'groff' directly.
Also you do _not_ need to create the index file befor
Hi Damian,
At 2023-07-01T03:11:37+1000, Damian McGuckin wrote:
[...]
> OK, I ran 'mmroff' and I can not see it works.
s/not/now/ ?
> Does that mean I can use all my 'groff' options to 'mmroff' for when I
> want to do index processing.
Yes, exactly. Here's the version of mmroff(1) man page from
Hi Damian,
At 2023-07-01T01:20:44+1000, Damian McGuckin wrote:
> .INITI P
> .IND item0
> .IND item1
> .IND item2
> .INDO
The foregoing gives good exercise to new groff mm indexing system
validation logic, which will show up early in the next release cycle.
$ ./build/test-groff -rRef=1 -mm -z EXP
mmroff is broken. It assumes that '-mm' is the first argument to 'groff'
I use '-ma4' to groff to force A4 before '-mm'.
So with 'mmroff', my document comes out in 'letter'. Not quite what I want
What does 'mmroff' do and I will fake it up.
Thanks - Damian
Pacific Engineering Systems Intern
Sorted.
The new system won't really work because it uses \n[%] which is not what I
want to get as a page number. I want \nP because I reset it to zero after
the abstract.
I looked at the ultimate documentation (the macros themselves).
I can see my old friend .IX which sends its argument an
My brain has gone to mush after trying to index this document.
I need other opinions.
Do we need a Table of Contents?
What words do people want indexed? Feel free to volunteer your own list.
What things do people looks for currently when they look up documentation?
Do I need to include each
14 matches
Mail list logo
