[self-follow-up with correction]
At 2024-01-19T18:56:37-0600, G. Branden Robinson wrote:
> This might be more accurately stated as:
>
> 2) \X behaves like .device used to (in groff 1.23.0 and earlier).
[correction follows]
And I repeat: this is _NOT_ a _hard_ prerequisite to expressing Unicode
s
Hi Deri,
At 2024-01-20T00:07:21+, Deri wrote:
> On Friday, 19 January 2024 21:39:57 GMT G. Branden Robinson wrote:
> > Right. Before I craft a lengthy response to this--did you see the
> > footnote?
>
> Yes, sorry, it didn't help. I'm just comparing output now with output
> in 1.23.0 and wha
On Friday, 19 January 2024 21:39:57 GMT G. Branden Robinson wrote:
> Hi Deri,
>
> At 2024-01-19T21:16:54+, Deri wrote:
> > On Tuesday, 16 January 2024 19:22:48 GMT G. Branden Robinson wrote:
> > > Or: Should device control commands affect the environment?
> > >
> > > I therefore propose to ch
Hi Deri,
At 2024-01-19T21:16:54+, Deri wrote:
> On Tuesday, 16 January 2024 19:22:48 GMT G. Branden Robinson wrote:
> > Or: Should device control commands affect the environment?
> >
> > I therefore propose to change this, and have the `\X` escape sequence
> > read its argument in copy mode.
On Tuesday, 16 January 2024 19:22:48 GMT G. Branden Robinson wrote:
> Or: Should device control commands affect the environment?
>
...
> I therefore propose to change this, and have the `\X` escape sequence
> read its argument in copy mode. That will make it work like the
> `device` request in g
Hi Lennart,
At 2024-01-18T15:45:55+, Lennart Jablonka wrote:
> Quoth John Gardner:
> > Thanks for reminding me, Branden. :) I've yet to get V7 Unix working with
> > the latest release of SimH, so that's kind of stalled my ability to develop
> > something in K&R-friendly C.
>
> I went ahead a
