Re: We have OSC 8 terminal hyperlink support now

2022-11-02 Thread G. Branden Robinson
At 2022-10-31T17:35:10+0100, Jakub Wilk wrote: > * G. Branden Robinson , 2021-10-02 14:02: > > less(1) only developed OSC 8 support in version 566, released about > > one year ago. Versions prior to that misinterpreted the OSC 8 escape > > sequence and would write parts of it to the terminal window

Re: We have OSC 8 terminal hyperlink support now

2022-10-31 Thread Alejandro Colomar
Hi Jakub! On 10/31/22 17:35, Jakub Wilk wrote: * Alejandro Colomar , 2021-10-02 18:45: Heh! Nice revival. I was curious why man: and not man://, What follows foo:// is the authority component (most often the host name); see RFC 3986 §3. So man://awk.1 is wrong, unless you put awk.1 in

Re: We have OSC 8 terminal hyperlink support now

2022-10-31 Thread Jakub Wilk
* Alejandro Colomar , 2021-10-02 18:45: I was curious why man: and not man://, What follows foo:// is the authority component (most often the host name); see RFC 3986 §3. So man://awk.1 is wrong, unless you put awk.1 in the DNS somehow. :-P -- Jakub Wilk

Re: We have OSC 8 terminal hyperlink support now

2022-10-31 Thread Jakub Wilk
* G. Branden Robinson , 2021-10-02 14:02: less(1) only developed OSC 8 support in version 566, released about one year ago. Versions prior to that misinterpreted the OSC 8 escape sequence and would write parts of it to the terminal window, an unsightly mess that would be sure to displease users

Re: We have OSC 8 terminal hyperlink support now

2021-10-06 Thread Alejandro Colomar (man-pages)
On 10/6/21 3:57 PM, Alejandro Colomar (man-pages) wrote: function pdfman() { if (($# == 0)); then     >&2 echo "Usage: ${FUNCNAME[0]} [man options] [[section] page ...] ..."; Oops! Since it only supports a single page, it should be: >&2 echo "Usage: ${FUNCNAME[0]} [man opti

Re: We have OSC 8 terminal hyperlink support now

2021-10-06 Thread Alejandro Colomar (man-pages)
Hi, Brandem! On 10/6/21 2:53 PM, G. Branden Robinson wrote: Hi, Alex! At 2021-10-02T20:08:03+0200, Alejandro Colomar (man-pages) wrote: On 10/2/21 7:45 PM, G. Branden Robinson wrote: There is the question of what to do if a man page cross reference is ambiguous, Nothing, IMO. Even if the m

Re: We have OSC 8 terminal hyperlink support now

2021-10-06 Thread G. Branden Robinson
At 2021-10-04T12:28:50-0400, James K. Lowden wrote: > What happens on such a system if you type > > $ man 2 open > > ? > > I think the system searches MANPATH or whatever, finds the first page > meeting the search criteria, and displays that. To see another page, > you'd have to use "-a"

Re: We have OSC 8 terminal hyperlink support now

2021-10-06 Thread G. Branden Robinson
Hi, Alex! At 2021-10-02T20:08:03+0200, Alejandro Colomar (man-pages) wrote: > On 10/2/21 7:45 PM, G. Branden Robinson wrote: > > > > There is the question of what to do if a man page cross > > > > reference is ambiguous, > > Nothing, IMO. > > Even if the man page cross reference is invalid (mayb

Re: We have OSC 8 terminal hyperlink support now

2021-10-04 Thread James K. Lowden
On Sun, 3 Oct 2021 00:57:35 +1000 "G. Branden Robinson" wrote: > There is the question of what to do if a man page cross reference is > ambiguous, perhaps due to a plethora of installed pages on the system. > (For example, I might have the Linux man-pages open(2) on my system as > well as the Ope

Re: We have OSC 8 terminal hyperlink support now

2021-10-02 Thread Alejandro Colomar (man-pages)
Hi, Branden! On 10/2/21 7:45 PM, G. Branden Robinson wrote: Hi, Alex! At 2021-10-02T18:45:58+0200, Alejandro Colomar (man-pages) wrote: I was curious why man: and not man://, so I had a look at what uri(7) says about it. Curiously, it talks about man:. That's a good question and one for whi

Re: We have OSC 8 terminal hyperlink support now

2021-10-02 Thread G. Branden Robinson
Hi, Alex! At 2021-10-02T18:45:58+0200, Alejandro Colomar (man-pages) wrote: > I was curious why man: and not man://, so I had a look at what uri(7) > says about it. Curiously, it talks about man:. That's a good question and one for which I have no answer. I'm happy to follow whatever the consen

Re: We have OSC 8 terminal hyperlink support now

2021-10-02 Thread Alejandro Colomar (man-pages)
Hi, Branden and John! On 10/2/21 4:57 PM, G. Branden Robinson wrote: Hi, John! At 2021-10-02T23:20:06+1000, John Gardner wrote: I know it's probably a bit early for this discussion, but somebody on GitHub raised a good question

Re: We have OSC 8 terminal hyperlink support now

2021-10-02 Thread G. Branden Robinson
Hi, John! At 2021-10-02T23:20:06+1000, John Gardner wrote: > I know it's probably a bit early for this discussion, but somebody on > GitHub raised a good question > > : > > > Why x-man-page? dnf reports that

Re: We have OSC 8 terminal hyperlink support now

2021-10-02 Thread G. Branden Robinson
Hi, John! At 2021-10-02T14:24:08+1000, John Gardner wrote: > That's one small step for a man... one giant leap for man(1)-kind. ;-) > Brilliant work! Thanks! We'll drag it into the 21st century by its gray hair... > I can't wait to update Mono.tmac > to inc

Re: We have OSC 8 terminal hyperlink support now

2021-10-02 Thread John Gardner
I know it's probably a bit early for this discussion, but somebody on GitHub raised a good question : Why x-man-page? dnf reports that yelp & khelpcenter provide man:// - but > has no providers for x-man-page:

Re: We have OSC 8 terminal hyperlink support now

2021-10-01 Thread John Gardner
Hi Brandon, That's one small step for a man... one giant leap for man(1)-kind. ;-) Brilliant work! I can't wait to update Mono.tmac to include it! Is there any reliable way for a macro-package to detect support for this at runtime? Also, I spotted a typo in

We have OSC 8 terminal hyperlink support now

2021-10-01 Thread G. Branden Robinson
Hi all, I'm pleased to report that I've landed a new feature in groff Git HEAD. The grotty(1) output driver now recognizes a new "link" device control subcommand and uses it to synthesize ECMA-48 OSC 8 escape sequences to pass hyperlink information to the terminal device. This means that, on ter