Re: groff man(7) `B` macro behavior with `\c`, and input traps

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

Re: groff man(7) `B` macro behavior with `\c`, and input traps

> > 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

Re: Zero Width Space

> > What about "input escape" Copy+pasta from my earlier post to a concurrent discussion in another thread: s/input escape/control suppressor/gi s/input escape/command suppressor/gi (This discussion appears to have been split betw

Re: [TUHS, groff] 1981 edition of AT&T Nroff/Troff User's Manual

> https://www.tuhs.org/Archive/Documentation/Manuals/Unix_4.0/Volume_1/C.1.2_NROFF_TROFF_Users_Manual.pdf Since PDF didn't exist in 1981, the document is either a scan or the result of a recent *roff run on ancient source. If it was made from source, it's an impressive testimonial to the longevity

Re: [TUHS, groff] 1981 edition of AT&T Nroff/Troff User's Manual

> > Since PDF didn't exist in 1981, the document is either a scan or the > result of a recent *roff run on ancient source. > It's most definitely a scan. Magnifying the pages reveals dust, surface details (grain and creases), and shadow falloff around the holes and edges. Each page is also titled

Re: [TUHS] Re: [TUHS, groff] 1981 edition of AT&T Nroff/Troff User's Manual

Well thank you both!!! ᐧ On Mon, Jun 6, 2022 at 10:01 AM wrote: > Douglas McIlroy wrote: > > > > > https://www.tuhs.org/Archive/Documentation/Manuals/Unix_4.0/Volume_1/C.1.2_NROFF_TROFF_Users_Manual.pdf > > > > Since PDF didn't exist in 1981, the document is either a scan or the > > result of a

Re: [TUHS] Re: [TUHS, groff] 1981 edition of AT&T Nroff/Troff User's Manual

Douglas McIlroy wrote: > > https://www.tuhs.org/Archive/Documentation/Manuals/Unix_4.0/Volume_1/C.1.2_NROFF_TROFF_Users_Manual.pdf > > Since PDF didn't exist in 1981, the document is either a scan or the > result of a recent *roff run on ancient source. If it was made from > source, it's an impre

Re: groff man(7) `B` macro behavior with `\c`, and input traps

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"

Re: install-font script (was: groff 1.23.0.rc2 readiness)

On Monday, 6 June 2022 06:38:00 BST G. Branden Robinson wrote: > Just within the past couple of days, on this list, it came to light that > our generation of Foundry files might be buggy, omitting the Ghostscript > font search path.[2] Hi Branden, Since you have moved the discussion here, I will

Re: Zero Width Space

Following this thread, I've been reminded of this classic. An old man speaks to his grandson: "When I was young, I looked across the lake and saw a mountain. As I grew up, I looked across the lake and saw so much more than a mountain. Now I am old; when I look across the lake, I see a mou

Re: Zero Width Space

Hi Ingo, On 6/5/22 19:09, Ingo Schwarze wrote: .B foo\& bar If that were a no-op, I wouldn't write it (why would I write something that does nothing???). In fact, it does *not* do anything in this particular situation either. [...] Or are you thinking about .TH TEST 1 .

Re: Zero Width Space

> I propose a radical solution to the problem of defining \&: return > to the cstr54 definition, Hear! Hear! > if we must find a convenient, shorter alternative, "null > character" seems the best choice, You must be joking. That would be a gratuitous clash in terminology for a large fraction of

Re: Zero Width Space

On Mon, 6 Jun 2022, Douglas McIlroy wrote: I propose a radical solution to the problem of defining \&: return to the cstr54 definition, Hear! Hear! I second that. if we must find a convenient, shorter alternative, "null character" seems the best choice, Please no. The concept of null is

Re: Zero Width Space

On Mon, Jun 06, 2022, Douglas McIlroy wrote: > > if we must find a convenient, shorter alternative, "null > > character" seems the best choice, > > You must be joking. That would be a gratuitous clash in > terminology for a large fraction of groff users. Everybody > who's ever written a C program

Re: groff man(7) `B` macro behavior with `\c`, and input traps

[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