Hey Branden and Group,
On Sat, 18 Jun 2022, G. Branden Robinson wrote:
> I sure wish someone would leak the Unix 4.0 (1981) troff sources.
The ditroff conversion before the releases of Documenter's Workbench?
> Maybe a shorter pole would be to write a cat2dit(1) for V7-era C.
For reviewing C
Hi Ingo,
At 2022-06-17T20:53:13+0200, Ingo Schwarze wrote:
> during the testing described below (which i foolishly expected to
> be minor), i tripped over several new candidates for regressions
> that look unrelated. This is not a serious report yet, i'll have to
> investigate in more detail and
Hi Branden,
during the testing described below (which i foolishly expected to
be minor), i tripped over several new candidates for regressions
that look unrelated. This is not a serious report yet, i'll have to
investigate in more detail and then report properly. The candidates
include the follo
Hi Ingo!
At 2022-06-06T09:18:01+0200, Ingo Schwarze wrote:
> So since .B uses .itc, and that appears to match Heirloom behaviour
> according to your research, it might be unwise to change that now.
I've changed it anyway. I now regard Heirloom's man(7) as buggy in this
respect. If I run Heirloo
Hi Branden,
> 4. Marking empty tbl(1) entries.
>
> There are other applications, but those are the ones I can think of
> immediately.
Specifying the point of alignment for tbl(1)'s numeric columns.
$ tbl | nroff | grep .
.TS
n.
\(Po
\(Po\&
1
23
456
7890
.T
At 2022-06-06T21:14:01+1000, John Gardner wrote:
> I haven't read the entirety of this thread, but why hasn't the name
> *"command suppressor"* or *"control suppressor"* been considered?
> AFAIK, \& has no other uses outside of an input line (diversions
> notwithstanding), so naming it *"input brea
[Warning: another long message, including SIMH PDP-11 output]
At 2022-06-06T12:17:30-0500, G. Branden Robinson wrote:
> It is disappointing that I couldn't get any useful information out of
> Unix V7 nroff. But I tried only the default device (Teletype Model
> 37), and maybe others are more perfo
Hi Ingo!
At 2022-06-06T09:18:01+0200, Ingo Schwarze wrote:
> G. Branden Robinson wrote on Sun, Jun 05, 2022 at 06:08:46PM -0500:
> > .\" Set arguments (or next input line if none) in bold style.
> > .de1 B
> > . itc 1 an-input-trap
>
> Ouch: .itc!
;-)
> > .B
> > .
> > foo
> >
> > Should "foo"
>
> And to allude to an another conversation we are currently having,
> including those that contain nothing but "\&", but *not* those that are
> completely empty, which would make you think that "\&" is a "zero-width
> non-breaking space" or a "zero-width non-printing character" rather than
> mere
Hi Branden,
G. Branden Robinson wrote on Sun, Jun 05, 2022 at 06:08:46PM -0500:
> [Warning: this message is long.]
Thanks for the thorough explanation.
> At 2022-06-05T19:09:53+0200, Ingo Schwarze wrote:
>> On a tangent, i just noticed that
>>
>> .TH TEST 1
>> .B foo\c
>> bar
>>
>> pr
[Warning: this message is long.]
Hi Ingo,
At 2022-06-05T19:09:53+0200, Ingo Schwarze wrote:
> On a tangent, i just noticed that
>
> .TH TEST 1
> .B foo\c
> bar
>
> prints "bar" in Roman font with mandoc(1), which seems correct to me,
> whereas it appears to print "bar" in bold with groff-
11 matches
Mail list logo
