Hi Branden,
G. Branden Robinson wrote on Thu, Jan 16, 2020 at 01:16:54AM -0500:
> gbranden pushed a commit to branch master
> in repository groff.
>
> commit d603c514e393ce5ce7fa1d936caf098c5da7973c
> Author: G. Branden Robinson
> AuthorDate: Sun Sep 22 04:56:55 2019 +1000
>
> **/*.man: El
Hi Ingo,
> 3. In tmac/groff_trace.7.man, the blank lines you changed to .P
>are inside .EX blocks. As far as i know, both blank lines
>and .P work portably in .nf mode and hence in .EX blocks and
>.Bd -unfilled and .Bd -literal.
They give very different results though. A blank line'
Hi,
seeing that Branden is currently working actively on groff, is anyone
willing to provide an OK for https://savannah.gnu.org/bugs/?57485 ?
TLDR: The point is that i have seen several manuals in a number of
different operating systems, both historical (around 1990) and modern
(around 2020) that
Hi Ingo,
On Thu, Jan 16 2020 at 06:56:09 PM, Ingo Schwarze wrote:
> seeing that Branden is currently working actively on groff,
I was trying to catch up all my unread mails, unfortunately last year
I was too busy to work for groff, hope this year will be better.
> is anyone willing to provide an
Ralph Corderoy wrote on Thu, Jan 16, 2020 at 05:07:38PM +:
> Ingo Schwarze wrote:
>> 3. In tmac/groff_trace.7.man, the blank lines you changed to .P
>>are inside .EX blocks. As far as i know, both blank lines
>>and .P work portably in .nf mode and hence in .EX blocks and
>>.Bd -un
Hi Ralph,
On Sun, Jan 05 2020 at 06:20:10 PM, Ralph Corderoy
wrote:
>> Werner wrote:
>> > I think the proper way for testing groff would be to make it run
>> > with a fuzzer,
>>
>> Yes, that would no doubt be useful.
> ...
>> is kind of orthogonal to developing a test suite, though.
> ...
>> A t
On Thu, Jan 16, 2020 at 06:56:09PM +0100, Ingo Schwarze wrote:
> TLDR: The point is that i have seen several manuals in a number of
> different operating systems, both historical (around 1990) and modern
> (around 2020) that give one or two arguments to .Dd. From the
> content of these arguments,
Hi Colin,
Colin Watson wrote on Thu, Jan 16, 2020 at 11:54:15PM +:
> On Thu, Jan 16, 2020 at 06:56:09PM +0100, Ingo Schwarze wrote:
>> TLDR: The point is that i have seen several manuals in a number of
>> different operating systems, both historical (around 1990) and modern
>> (around 2020) t
At 2020-01-03T14:09:46+0100, Ingo Schwarze wrote:
[what senior engineers should and should not be doing]
> This seems excessively strict to me.
Yes, in retrospect I was trying on a somewhat exaggerated position for
size.
> Yes, i know rms@ is no longer writing much new code nowadays.
Not the exa
At 2019-12-31T13:59:26+0100, Ingo Schwarze wrote:
> You are right, i didn't realize "X$" is an old idiom from per-POSIX
> times and not needed with POSIX shells.
No worries. I hope I didn't come across too harshly; the construction
makes my eyes bleed. :-O
> I did not commit these yet such that
At 2019-12-31T13:11:49+0100, Ingo Schwarze wrote:
> I won't touch this here document until it's clear whether there
> is an ksh(1) bug. Working on shell bugs tends to be very time
> comsuming, so there may be a substantial delay, which shouldn't
> be a problem because this doesn't harm groff's use
At 2019-12-31T09:02:52+, Ralph Corderoy wrote:
> It looks like the test harness needs a common shell script that provides
> convenience functions. Then the test script can read more like
>
> # All run under `set -eu' with a trap on EXIT.
>
> title 'Check -Tlatin1's \(oq'
>
> in=
12 matches
Mail list logo
