discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <sdaoden@yandex.com>
To: discuss@mdocml.bsd.lv
Subject: Re: Linking in mdoc(7)
Date: Wed, 11 Mar 2015 11:07:46 +0100	[thread overview]
Message-ID: <20150311100746.7FfnAcAq%sdaoden@yandex.com> (raw)
In-Reply-To: <54FFF740.3080201@bsd.lv>

Hello Kristaps,

Kristaps Dzonsons <kristaps@bsd.lv> wrote:
 |Steffen,
 |
 |I don't understand these problems.  In mandoc(1), the previously
 |enclosed patch completely implements the `Ix' functionality, both in
 |terms of `Sx' and the nascent (badly named?) `Lkx'.  It works.  I've
 |been using it happily to build index tables and chapter references
 |that jump to functions, etc., etc.
 |
 |As for groff, can't it just (via doc.tmac) throw away the `Ix'
 |arguments and that's that?  And if we want an `Lkx' (which I strongly

Of course.  It really seems that unknown requests are (by default
even silently) ignored, luckily.

 |advise for arbitrary link names), it can be a duplicate of `Lk'.
 |grohtml can't even link `Sx' and `Sh': it just italices the arguments
 |to the former!  (This may have changed in recent groff.)  So if it
 |ignores `Ix' and continues in doing what it already does with `Sx',
 |what exactly is the loss?

troff(1) based mdoc(7) compatibility.  At a minimum until
i completely rewrite the mdoc(7) macros as posted (assuming that
noone else will spend the time necessary for that -- and has
anyone ever thought about cross-financing a GSoC student for such
a basic thing like manual page usability?).  If it can possibly
work then depends on how you define the semantics, anchors that
cannot be ".ds"'d and link content that cannot be ".if '''"d will
never work.  Of course ;)

And do you really plan to support these new commands only for HTML
and PDF output?  What a pity!  Better interactivity on the TTY is
what really strives me.  (I'm not an emacs user..)
Ciao,

--steffen
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  parent reply	other threads:[~2015-03-11 10:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <sfid-H20150308-171308-+043.19-1@spamfilter.osbf.lua>
2015-03-08 16:12 ` Kristaps Dzonsons
2015-03-09  6:29   ` Thomas Klausner
2015-03-09  6:38     ` Anthony J. Bentley
2015-03-09  8:46       ` Kristaps Dzonsons
2015-03-09 11:12         ` Joerg Sonnenberger
2015-03-09 11:34           ` Kristaps Dzonsons
2015-03-09 11:09   ` Steffen Nurpmeso
2015-03-09 11:46     ` Ingo Schwarze
2015-03-09 12:25       ` Kristaps Dzonsons
2015-03-09 15:36         ` Kristaps Dzonsons
2015-03-10 16:30           ` Steffen Nurpmeso
2015-03-11  8:05             ` Kristaps Dzonsons
2015-03-11  8:15               ` Anthony J. Bentley
2015-03-11 10:07               ` Steffen Nurpmeso [this message]
2015-03-09 13:11       ` Steffen Nurpmeso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150311100746.7FfnAcAq%sdaoden@yandex.com \
    --to=sdaoden@yandex.com \
    --cc=discuss@mdocml.bsd.lv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).