Anton Shterenlikht:
> I want the cover page to show no page number, the
> front page to show no number, and the first normal
> page to show page number 2. All pages after that
> I want to be numbered consequtively.
This is complicated and couldn't do it without fix-
ing mm. Maybe it's not wo
From anton@gmail.com Thu Aug 23 10:42:55 2012
Anton Shterenlikht:
> I want the cover page to show no page number, the
> front page to show no number, and the first normal
> page to show page number 2. All pages after that
> I want to be numbe
> By the way, this innocuous error message could be mended by
> modifying mm's .GETST so that on the first pass it would initialize
> the string passed in the second argument with a dummy value instead
> of skipping its creation.
>
> Werner, would you approve it?
Of course. Do you want to take
On 22/08/12 23:49, Anton Shterenlikht wrote:
Thank you. Here's a small document:
\" process with mm
I'm not an mm user, but surely this is wrong? It introduces a blank
input line *before*...
.PGNH
.PF "''\*(DT''"
.COVER
...which, according to the groff_mm manpage, is not allowed. If yo
Anton Shterenlikht:
> However, I'm very reluctant to mess with mm/ms
> macro definitions locally. I'll live with the page
> number on the front page. The most annoying thing
> was the page number on the cover page, which is
> solved by .hd@set-page -1.
As a temporary solution, you can c
From keith.d.marsh...@ntlworld.com Thu Aug 23 13:28:51 2012
On 22/08/12 23:49, Anton Shterenlikht wrote:
> Thank you. Here's a small document:
>
> \" process with mm
I'm not an mm user, but surely this is wrong? It introduces a blank
input
On 23/08/12 13:57, Anton Shterenlikht wrote:
However, the next page will still be number 2, and I don't know
how to fix that, (inserting .pn requests doesn't seem to have the
desired effect).
That is solved by (thanks to Anton Shepelev)
.hd@set-page -1
But that isn't really a good solution!
Keith Marshall:
> > That is solved by (thanks to Anton Shepelev > ton@gmail.com>)
> >
> > .hd@set-page -1
> >
> But that isn't really a good solution! It re-
> quires getting your hands dirty with the internal
> (private) details of the macro implementation.
>
> This is similar to
From anton@gmail.com Thu Aug 23 14:43:42 2012
Keith Marshall:
> > That is solved by (thanks to Anton Shepelev > ton@gmail.com>)
> >
> > .hd@set-page -1
> >
> But that isn't really a good solution! It re-
Now that I sorted
Anton Shterenlikht:
> Now that I sorted out my empty lines, I get the
> cover page with no number.
>
> I tried groff -n option, but it seems to change
> the number of only the cover page, which is not
> shown anyway. The numbers of other pages are unaf-
> fected. Is this the expected beh
On 23/08/12 14:42, Anton Shepelev wrote:
You should not need to do this; there surely must be a public
interface to support what you are trying to achieve, without
subverting package internals?
I agree, but I didn't find a public mechanism to do that.
Does the attached achieve the desired eff
Keith Marshall:
> > I agree, but I didn't find a public mechanism to
> > do that.
>
> Does the attached achieve the desired effect?
> Agreed, it isn't intuitive: it's very picky about
> the placement of the reassignment of register 'P',
> and you have to set it to less than zero for it,
>
Hi,
> Yes, and this is exactly what hd@set-page does. The documentation
> doesn't say that P is not read-only. I consider hd@set-page as a
> setter of the field P and therefore preferable to setting P directly.
> If it was not so trivial my method would be less likely to break
> anything.
To my
Ralph Corderoy:
> > Yes, and this is exactly what hd@set-page does.
> > The documentation doesn't say that P is not
> > read-only. I consider hd@set-page as a setter
> > of the field P and therefore preferable to set-
> > ting P directly. If it was not so trivial my
> > mehtod would
On 23/08/12 18:26, Anton Shepelev wrote:
Thanks, I missed the piece about hd*sect-pg. My
version is definitely better then.
Except for one fairly important issue: you are advocating exposure of
what *should* be a private interface, (according to naming convention),
and is thus *entirely*
Keith Marshall:
> > Thanks, I missed the piece about hd*sect-pg.
> > My version is definitely better then.
>
> Except for one fairly important issue: you are ad-
> vocating exposure of what *should* be a private in-
> terface, (according to naming convention), and is
> thus *entirely* spe
I wrote:
> My other suggestion...
Correction: It is actually Anton Shterenlikht's,
while I only proposed a way to implement it.
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
17 matches
Mail list logo
