[e9e92ee00811f7d0fcbde415346f7f4f7be14528] missed one

2022-09-06 Thread Steffen Nurpmeso
P.S.: i overtook this name change to my roff clone, shall that
ever spring into real existance.  You have a credit, please
complain if you do not want to be named in THANKS.

diff --git a/tmac/mdoc/doc-common b/tmac/mdoc/doc-common
index 6c9093a876..29ee7f8c7b 100644
--- a/tmac/mdoc/doc-common
+++ b/tmac/mdoc/doc-common
@@ -345,7 +345,6 @@
 .  ds doc-topic-name \" empty
 .  ds doc-volume LOCAL
 .  ds doc-section \" empty
-.  ds doc-command-name
 .
 .  if !"\$1"" \
 .ds doc-document-title "\$1



--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)



Re: [e9e92ee00811f7d0fcbde415346f7f4f7be14528] missed one

2022-09-06 Thread G. Branden Robinson
At 2022-09-06T16:22:42+0200, Steffen Nurpmeso wrote:
> P.S.: i overtook this name change to my roff clone, shall that
> ever spring into real existance.  You have a credit, please
> complain if you do not want to be named in THANKS.

If I've earned it, I don't mind it.  Evaluating the antecedent is the
hard part.  :)

> diff --git a/tmac/mdoc/doc-common b/tmac/mdoc/doc-common
> index 6c9093a876..29ee7f8c7b 100644
> --- a/tmac/mdoc/doc-common
> +++ b/tmac/mdoc/doc-common
> @@ -345,7 +345,6 @@
>  .  ds doc-topic-name \" empty
>  .  ds doc-volume LOCAL
>  .  ds doc-section \" empty
> -.  ds doc-command-name
>  .
>  .  if !"\$1"" \
>  .ds doc-document-title "\$1

Thanks, Steffen.  I have applied this to my working copy.

Regards,
Branden


signature.asc
Description: PGP signature


Re: [e9e92ee00811f7d0fcbde415346f7f4f7be14528] missed one

2022-09-06 Thread Steffen Nurpmeso
Hello Branden.

G. Branden Robinson wrote in
 <20220906205844.xbo54jzk2v7jscvf@illithid>:
 |At 2022-09-06T16:22:42+0200, Steffen Nurpmeso wrote:
 ...
 |Thanks, Steffen.  I have applied this to my working copy.

It would be _tremendous_ if \X'tty: link' would get the
possibility to create ID-only anchors, Branden.  Otherwise i have
to use a dummy link target (currently the number-sign), and then
there is indeed a link target.
Now, _if_ that less(1) pull request gets through, with

  ^O^I Search for an OSC 8  in the file.
  ^O^P Go to previous OSC 8 link.
  ^O^N Go to next OSC 8 link.
  ^O^O Open current OSC 8 link with LESSOSC8OPEN.

then moving forward and backward via ^O^P and ^O^N will find those
dummy links, but they are only document-local anchors.

I mean, that is at least my idea for this, simply taking the HTML
way of doing things over, so that \X'tty: link #ID' searches for
and finds a document local \X'tty: link id=ID'.

I do like your idea of simply using one "link", and have any
number of user-defined colon-separated KEY=VALUE pairs.  With just
two issues, for one i would use colons for separators also on the
grotty side, so that whitespace in the input becomes possible, and
then i would really, really long for the mentioned only-ID aka
anchor thing.  That would truly be tremendous!

Ciao, and good night!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)



Re: [e9e92ee00811f7d0fcbde415346f7f4f7be14528] missed one

2022-09-06 Thread Steffen Nurpmeso
Oh!

Steffen Nurpmeso wrote in
 <20220906224118.jh2ju%stef...@sdaoden.eu>:
 |G. Branden Robinson wrote in
 | <20220906205844.xbo54jzk2v7jscvf@illithid>:
 ||At 2022-09-06T16:22:42+0200, Steffen Nurpmeso wrote:
 ...
 |It would be _tremendous_ if \X'tty: link' would get the

Actually i think it even has a bug, Branden.  It is

  `OSC` `8` `;` `params` `;` `URI` `ST`

where params are colon-separated.  But if i say
\X'tty: link # id=a' then it generates

  ^[]8;:id=a;#^[\3

aka already the first parameter "is separated" with a colon.
Maybe not a real bug, but surely the colon is redundant.
(Actually my less(1) pull request will not find the IDs my mdocmx
produces via your grotty thing because of it.  Hm.  Well, we break
out if we cannot find the = in the K=V, and ;: is an empty
parameter.  Sigh.  I have to make this more robust in that non-K=V
parameter is _not_ bogus if it is initially empty.  Bugs anywhere!)

Ciao.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)



Re: [e9e92ee00811f7d0fcbde415346f7f4f7be14528] missed one

2022-09-06 Thread Steffen Nurpmeso
Steffen Nurpmeso wrote in
 <20220906231824.-4way%stef...@sdaoden.eu>:
 ...
 |(Actually my less(1) pull request will not find the IDs my mdocmx
 |produces via your grotty thing because of it.  Hm.  Well, we break
 |out if we cannot find the = in the K=V, and ;: is an empty
 |parameter.  Sigh.  I have to make this more robust in that non-K=V
 |parameter is _not_ bogus if it is initially empty.  Bugs anywhere!)

The "standard" says

  `params` is an optional list of `key=value` assignments,
  separated by the `:` character. Example:
  `id=xyz123:foo=bar:baz=quux`. Currently only the `id` key is
  defined, see below. These parameters allow future ext endability
  of this feature. In the typical case no parameters are defined,
  in that case obviously the two semicolons have to be present
  next to each other.

So i mean i am not _that_ wrong in claiming that a parameter
without an = in the expected K=V is bogus.  However, it seems more
robust to allow empty parameters in the block of parameters.

Good night!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)



Re: [e9e92ee00811f7d0fcbde415346f7f4f7be14528] missed one

2022-09-07 Thread Steffen Nurpmeso
P.S.:

Steffen Nurpmeso wrote in
 <20220906232237.izz2i%stef...@sdaoden.eu>:
 |Steffen Nurpmeso wrote in
 | <20220906231824.-4way%stef...@sdaoden.eu>:
 ...
 ||(Actually my less(1) pull request will not find the IDs my mdocmx
 ...

I updated the pull request with an additional fix commit that
makes the code smaller and much more robust, enabling it to deal
with empty parameters, only ignore bogus ones etc.  So we deal
with grotty as-is.

I would still hope for a possibility to create anchor-only OSC 8.

Ciao, Branden.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)



Re: [e9e92ee00811f7d0fcbde415346f7f4f7be14528] missed one

2022-09-08 Thread Steffen Nurpmeso
Hello Branden,

..again, and sorry, for the noise..

Steffen Nurpmeso wrote in
 <20220907210913.drf4v%stef...@sdaoden.eu>:
 |P.S.:
 ...
 |||(Actually my less(1) pull request will not find the IDs my mdocmx
 ...
 |I updated the pull request with an additional fix commit that
 ...
 |I would still hope for a possibility to create anchor-only OSC 8.

Actually i will update it again with

osc8_inspect(): ignore "#[no ID]" local anchor URIs..

Like in HTML #ID are in-document local anchor references.
An URI # without ID does not lead anywhere usually.

Ignore them in the sole case that there also was an id= parameter,
meaning this OSC 8 construct is meant to *create* a local anchor.

Like this less(1) will be capable to deal with local anchors
generated by grotty(1)'s 1.23[.0] \X'tty: link' command.
(Which, perspectively, will be used for interactive Unix manual
pages.)

Whether it will make it i cannot tell.  But i can tell you
i _love_ to use the interactive manual pages since 2014.
Of course, only for the programs i created myself, but that is
a pity!

Ciao.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)