Re: macOS Terminal man page URL format

Hi John, At 2023-02-16T15:49:14+1100, John Gardner wrote: > > $ (unset GROFF_TYPESETTER; make -j check) > > I ran `GROFF_TYPESETTER= make check` and—as I expected—the tests > passed. Kick ass! The fix will be in my next push. > > I don't agree; when writing a test suite, one should eliminate a

Re: macOS Terminal man page URL format

Hi Branden, > $ (unset GROFF_TYPESETTER; make -j check) I ran `GROFF_TYPESETTER= make check` and—as I expected—the tests passed. > I don't agree; when writing a test suite, one should eliminate as many > confounding variables (in the experimental sense) as possible Yes, which is why I suggested

Re: macOS Terminal man page URL format

At 2023-02-16T15:34:57+1100, John Gardner wrote: > > ...wait. Did you configure your groff build to use one of the > > terminal devices as the default typesetter? Or maybe you have > > GROFF_TYPESETTER set a terminal device in the environment? > > I do, actually >

Re: macOS Terminal man page URL format

> ...wait. Did you configure your groff build to use one of the terminal > devices as the default typesetter? Or maybe you have GROFF_TYPESETTER > set a terminal device in the environment? I do, actually

Re: macOS Terminal man page URL format

Hi John, At 2023-02-16T15:09:06+1100, John Gardner wrote: > Many thanks. All but one of the tests are passing now, which is the > same one you're having troubles reproducing the failure of: > > > > FAIL: tmac/tests/an_use-input-traps-correctly.sh > > > > I found this very weird but I could not re

Re: macOS Terminal man page URL format

Hi Branden, I've pushed fixes for these. > Many thanks. All but one of the tests are passing now, which is the same one you're having troubles reproducing the failure of: > > FAIL: tmac/tests/an_use-input-traps-correctly.sh > > I found this very weird but I could not reproduce this test failure

Re: macOS Terminal man page URL format

Hi John, At 2023-02-11T10:19:08+1100, John Gardner wrote: > However, when I ran `make check` in my checkout directory, 7 of the > tests failed (full details in the attached log file): > > FAIL: tmac/tests/an_use-input-traps-correctly.sh I found this very weird but I could not reproduce this test

Re: "make check" failing on macOS (was: macOS Terminal man page URL format)

> > I just want to compare 2 byte streams in a shell script without using > temporary files. Just out of curiosity: why? The test directory is already polluted with artefacts during the course of the test-run: I don't see why creating a few more is burdensome. In any case, the difference between

"make check" failing on macOS (was: macOS Terminal man page URL format)

Hi John, At 2023-02-11T10:19:08+1100, John Gardner wrote: > Yes, it builds successfully now (macOS 12.6.3). I ran `make install` > and the installed Groff seems to be working perfectly. Excellent! > However, when I ran `make check` in my checkout directory, 7 of the > tests failed (full details

Re: macOS Terminal man page URL format

Hi John, Any luck with this? We have two reports from macOS > 12.0 users that the assert.h-related compilation error is fixed in groff Git HEAD. At 2023-02-06T15:03:33-0600, G. Branden Robinson wrote: [...] > Right, sorry. You'll have to apply the patches to a system _in situ_ > and I forgot ab

Re: macOS Terminal man page URL format

Knowing Apple, the *x-man-page://* scheme was intended for internal use between userland programs; a similar protocol exists for looking up a word's definition: *x-dictionary:harangue*. However, the nature of macOS's LaunchServices makes it impossible (or at least incredibly difficult) for any supp

Re: macOS Terminal man page URL format

Hi John, At 2023-02-07T07:24:52+1100, John Gardner wrote: [I wrote:] > > I would prefer to hold macOS up to ridicule in this respect in hopes > > of motivating its users (and developers) to standardize on > > something. > > By "standardise", are you specifically referring to a *de jure* > standar

Re: macOS Terminal man page URL format

> > I would prefer to hold macOS up to ridicule in this respect in hopes of > motivating its users (and developers) to standardize on something. By "standardise", are you specifically referring to a *de jure* standard? macOS's x-man-page:// scheme is only a *de facto* standard, but it's by far th

Re: macOS Terminal man page URL format

Hi John, At 2023-02-07T06:26:22+1100, John Gardner wrote: > Then how about a callback? It could be called with the relevant > parameters, and authors can use plain ol' Roff to specify the > hyperlink format. That creates more places for something to go wrong. Also I don't want people to get the

Re: macOS Terminal man page URL format

Hi Branden, Having a configurable prefix/schema isn't going to cut it. > Then how about a callback? It could be called with the relevant parameters, and authors can use plain ol' Roff to specify the hyperlink format. but I have to say I really hate this and I want macOS to get its act > togethe

Re: macOS Terminal man page URL format

Hi John, At 2023-02-06T18:53:10+1100, John Gardner wrote: > So the exact URL format *does* need to be configurable, Please review, apply, and test the attached patch. > preferably with a separate string for apropos(1) links, if supported > (which would logically default to the `an*MR-scheme` str

Re: macOS Terminal man page URL format

Hi John, At 2023-02-06T18:53:10+1100, John Gardner wrote: > While I *strongly* advocate for the man:name(section) syntax (because > it essentially dates right back to the earliest man pages), it would > be remiss of me to ignore the other formats listed above. > > > But...ugh! I don't remember th

Re: macOS Terminal man page URL format

> > And since it's specific to the macOS Terminal application It's indicative of a much larger issue — there's no formal, standardised scheme for man page URLs. I encountered many variants

Re: macOS Terminal man page URL format

Hi John! At 2023-02-06T15:19:10+1100, John Gardner wrote: > > The an (man) macro package can now produce clickable hyperlinks > > within terminal emulators > > It might be worth clarifying for macOS users that the hyperlinks use a > protocol incompatible with Apple's: “*man:printf(3)*” is used in