Hi Klemens,
Ingo Schwarze wrote on Tue, Feb 18, 2020 at 04:30:53PM +0100:
> While i don't strongly object to the patch, it might be worth holding
> off a bit on manually tagging of .Sh given that even automatic
> tagging isn't done for that macro yet. Which would mean postponing
> this patch unt
Hi Klemens,
Ingo Schwarze wrote on Tue, Feb 18, 2020 at 04:30:53PM +0100:
> Klemens Nanni wrote on Mon, Feb 17, 2020 at 05:19:27PM +0100:
>> Patch was done with a VIM macro by adding a new line after each `.Sh'
>> line with the respective name but lowercased, so no typos in the added
>> strings.
Ingo Schwarze wrote in
<20200218160703.gb27...@athene.usta.de>:
|Hi,
|
|Steffen Nurpmeso wrote on Tue, Feb 18, 2020 at 04:52:48PM +0100:
|
|> i just want to add that there is still the mdocmx mdoc macro
|> extension available, and is working fine for more than half
|> a decade. I have not p
Hi,
Steffen Nurpmeso wrote on Tue, Feb 18, 2020 at 04:52:48PM +0100:
> i just want to add that there is still the mdocmx mdoc macro
> extension available, and is working fine for more than half
> a decade. I have not ported that to groff 1.22.4, but it is
> available for groff 1.22.3. It can mu
Hello.
I have not followed this thread but
Ingo Schwarze wrote in
<20200218153053.ga27...@athene.usta.de>:
|Klemens Nanni wrote on Mon, Feb 17, 2020 at 05:19:27PM +0100:
|
|> I'd like to commit this soon, it allows me to jump to the command I'm
|> looking for, e.g. ":tx509" shows me the synop
Hi Klemens,
Klemens Nanni wrote on Mon, Feb 17, 2020 at 05:19:27PM +0100:
> I'd like to commit this soon, it allows me to jump to the command I'm
> looking for, e.g. ":tx509" shows me the synopsis right away.
>
> FWIW, some Linux distributions ship with separate manuals, e.g. x509(1SSL).
Yes, t
> I like the idea!
I agree.
> To me it would be more logical to put .Tg above .Sh, but that is a minor
> thing.
I also think that it would better to place .Tg above .Sh .
On Mon, Feb 17, 2020 at 11:20:34PM +0100, Remi Locherer wrote:
> On Mon, Feb 17, 2020 at 05:19:27PM +0100, Klemens Nanni wro
On Mon, Feb 17, 2020 at 11:42:48PM +0100, Theo Buehler wrote:
> Without tags I currently achieve pretty much the same by doing "/^X509"
> or "/^S_CLIENT" etc. However, having to know the special trick for each
> page (if there is one) is annoying, so I think this is an improvement.
This is not sema
On Mon, Feb 17, 2020 at 05:19:27PM +0100, Klemens Nanni wrote:
>
> I'd like to commit this soon, it allows me to jump to the command I'm
> looking for, e.g. ":tx509" shows me the synopsis right away.
Without tags I currently achieve pretty much the same by doing "/^X509"
or "/^S_CLIENT" etc. Howe
On Mon, Feb 17, 2020 at 05:19:27PM +0100, Klemens Nanni wrote:
>
> I'd like to commit this soon, it allows me to jump to the command I'm
> looking for, e.g. ":tx509" shows me the synopsis right away.
>
> FWIW, some Linux distributions ship with separate manuals, e.g. x509(1SSL).
>
> Patch was do
I'd like to commit this soon, it allows me to jump to the command I'm
looking for, e.g. ":tx509" shows me the synopsis right away.
FWIW, some Linux distributions ship with separate manuals, e.g. x509(1SSL).
Patch was done with a VIM macro by adding a new line after each `.Sh'
line with the resp
11 matches
Mail list logo
