Ulrich --
On Mon, Nov 08, 2021, Ulrich Lauther wrote:
> I know that .SPACE | moves me to some distance from
> the top of the page, though I cannot find this knowledge in mom's
> documentation.
It's in the entry for 'sp' in the groff info manual.
> A naive person (like me) would hope, that a nega
On 11/8/21, Ralph Corderoy wrote:
> Bug. CSTR 54 doesn't allow it, nor does
> info groff 'Changing Type Sizes' | less
It doesn't seem quite that clear-cut to me. Neither of those sources
explicitly states what *roff does with additional parameters to .ps,
or with nonnumeric trailing charact
On 11/8/21, Peter Schaffter wrote:
> Not all punctuation or trailing characters are ignored.
>
> $ printf ".ps 12.5\n.tm \\\n[.s]\n" | groff -z
> 12.5
> $ printf ".ps 12:5\n.tm \\\n[.s]\n" | groff -z
> 1
> $ printf ".ps 12&5\n.tm \\\n[.s]\n" | groff -z
> 1
Right, but those are behaving as d
Hi Axel & Robert,
At 2021-10-28T20:17:43+0200, Axel Kielhorn wrote:
[...]
> make[1]: *** No rule to make target `tmac/mdoc/doc-common', needed by
> `all-am'. Stop.
[...]
At 2021-11-07T08:35:22-0500, Robert Goulding wrote:
> On Chromebook (Debian buster), make fails with:
>
> make[1]: *** No ru
On Mon, Nov 08, 2021, Dave Kemper wrote:
> Yeah, in fact, groff ignores numbers following several marks of
> punctuation besides the comma, and warns about none, even with all
> warnings turned on.
>
> $ printf '.ps 12\nword\n' | groff -Z -ww > test.out
> $ printf '.ps 12.5\nword\n' | groff -Z -ww
Hi Ralph,
i agree with (almost) all you are saying in this mail.
Ralph Corderoy wrote on Mon, Nov 08, 2021 at 02:05:00PM +:
> Ingo Schwarze wrote:
>> 3. Using your own replacement functions for Standard C and/or
>> POSIX functions is a bad idea because:
>>
>> 3.1. It makes the code har
I wrote:
> glyph.c:42:estrdup failed: 31415 'foo bar xyzzy...'
I forgot progname, i.e. the basename of argv[0].
troff:glyph.c:42:estrdup failed: 31415 'foo bar xyzzy...'
--
Cheers, Ralph.
Hi Ingo,
> If the intention of strsave() was to replace strdup(), then the
> correct implementation would have been
>
> size_t sz = strlen(s) + 1;
> char *p = malloc(sz);
> if (p != NULL)
> memcpy(p, s, sz);
> return p:
An estrdup() would be:
if (!s)
Hi Ingo,
> 3. Using your own replacement functions for Standard C and/or
> POSIX functions is a bad idea because:
>
> 3.1. It makes the code harder to read and audit for experienced
> programmers. Instead of being able to use their knowledge
> of standards, they have to figure o
Hi Dave,
> Yeah, in fact, groff ignores numbers following several marks of
> punctuation besides the comma, and warns about none, even with all
> warnings turned on.
...
> $ printf '.ps 12@5\nword\n' | groff -Z -ww | diff - test.out | wc
> 0 0 0
>
> > Sounds like a bug.
>
> Bug,
On 10/28/21, Ralph Corderoy wrote:
> Perhaps the code is doing the equivalent of atoi(3) and ignoring errors
> rather than something more akin to strtol(3) with care to prime errno(3)
> beforehand.
Yeah, in fact, groff ignores numbers following several marks of
punctuation besides the comma, and
11 matches
Mail list logo
