Hello ladies and gents. I'm trying to convince mom to give me a
page header on every page, including the first. In desperation,
I've even tried .HEADER_ON_FIRST_PAGE but she's having none of
it. Can it be done ? I don't need or want a document header, if
that matters, so .DOCHEADER OFF.
Thanks in
On 2023-04-22 16:22 -0400, Peter Schaffter wrote:
> On Sat, Apr 22, 2023, Frederic Chartier wrote:
> > I'm trying to convince mom to give me a page header on every
> > page, including the first.
>
> With the docheader turned off, insert the macro .HEADER immediately
&g
I've stumbled on another problem with -mom. There is a table at
the bottom of a page. After the table, something inserts what
behaves like a line feed and Groff warns that
[mom]: '2023-04-24.mom', macro TE, line 61:
Insufficient room for label, caption, and/or source after
On 2023-04-24 03:49 +0200, Oliver Corff wrote:
> I cannot use xterm, uxterm and Eterm on my system because of the high
> screen resolution; those terminal windows appear as tiny stamps which do
> not accept the Ctrl-+ resizing command.
With XTerm, the font can be set in three ways that I know of.
On 2023-04-24 14:55 -0400, Peter Schaffter wrote:
> I've never seen this behaviour before. It's been a while since I
> needed tbl(1) in a mom document so I'm thinking it crept in during
> one of the past year's bazillion commits. Most likely something to
> do with tbl(1) or with gropdf(1). At a
On 2023-04-24 21:59 -0400, Peter Schaffter wrote:
> On Mon, Apr 24, 2023, Frederic Chartier wrote:
> > I'm running groff 1.22.3, by the way. It's been patched but not
> > since 2016 so if it's bugs I'm seeing, they're not new.
>
> Can you check
I'm having trouble controlling the margins with -mom, especially
the right one. Consider this input :
.PAPER A4
.PRINTSTYLE TYPESET
.L_MARGIN 1c
.R_MARGIN 1c
.DOCHEADER OFF
.FOOTERS
.FOOTER_ON_FIRST_PAGE
.START
.PP
Some text. Some text. Some text. Some text. Some text. Some text.
Some text. Some t
On 2023-04-27 21:18 -0400, Peter Schaffter wrote:
> On Thu, Apr 27, 2023, Frederic Chartier wrote:
> > I'm having trouble controlling the margins with -mom... L_MARGIN
> > is honoured but R_MARGIN is ignored. I must be doing something
> > wrong, but what ?
>
>
Until now, my dealings with tbl(1) have been infrequent, casual
and pleasant. This time, I need actual control over the widths
of the columns. Specifically, I want column 1 to be exactly as
wide as its contents requires, columns 3 and 4 to have specific
(and different) widths and column 2 to take u
On 2023-04-28 16:39 -0500, G. Branden Robinson wrote:
> At 2023-04-28T23:18:34+0200, Frederic Chartier wrote:
> > Specifically, I want column 1 to be exactly as wide as its
> > contents requires, columns 3 and 4 to have specific (and
> > different) widths and column 2 to
On 2023-04-28 16:39 -0500, G. Branden Robinson wrote:
> Per tbl(1) from groff 1.23.0:
> [...]
> Ordinarily, a table entry is typeset rigidly. It is not filled,
> broken, hyphenated, adjusted, or populated with additional inter???
> sentence space.
This sentence was added in version
On 2023-05-03 09:29 -0500, G. Branden Robinson wrote:
> At 2023-05-03T09:07:03-0400, Douglas McIlroy wrote:
>
> > rationale for allowing removal of read-only registers
> > [includes :]
> >
> > It simplifies documentation
>
> This, I would quibble with. I feel morally compelled to document this
>
On 2024-03-17 15:52 -0500, G. Branden Robinson wrote:
> A. GNU roff and Sun troff are, historically, heavyweights in terms of
> users served. Apparently, man page users on these systems have been
> accepting of adjustment ("full justification") for decades.
Perhaps "suffering" would be
On 2024-05-20 09:00 -0500, G. Branden Robinson wrote:
> For grins, and for a data point from elsewhere in GNU-land, GNU troff is
> pretty robust to this sort of thing. Much as I might like to boast of
> having improved it in this area, it appears to have already come with
> iron long johns courte
14 matches
Mail list logo
