discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: Linking in mdoc(7)
Date: Wed, 11 Mar 2015 17:05:20 +0900	[thread overview]
Message-ID: <54FFF740.3080201@bsd.lv> (raw)
In-Reply-To: <20150310163053.I3TjLbTZ%sdaoden@yandex.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

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
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?

Best,

Kristaps

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJU//dAAAoJEMT2SUY9XBESJ/IP/i8FgiUB4BI+Z2KaDTM9ROww
3VHizu22FmpfLuzzjlj5QvyzRqT8H6K/aMHwzI7n20qMDekneUkNpLmkb29FHrC1
vJl57on9wXJGeQMfSSzBjpQPNGoud5Ag0e5eK9qcrvOufANB2lCi9KOKhqt0Pjk8
+dg+so3DXCf40XTSzxWgr5HzMFWFZgONZuhHfDfUMwhwjqZPx8O9w1suNfvCkcAS
czFe1j1mssBC7G2KBWmZI4J6yIlzC3rGZcEk5sxzlSsnuxeymcuLYXiZ8QV0qQAm
UslqF74W5d84oU5XHfN1NZUZjrEbbC93DvM/m92KYD09E3Zr9p8qR1nTHN6mTKda
ieO415F98EvCIC3AwukgaxzgC09g+B95nhVCV2NZhTRYO2vr7XXhUPM80ZRzLumI
TU8c6KR5gAk7ou17xj8kdFugVjxC8uu8kRzwmgqZw2Oog7ZRJAH7UV+9DWwrX6Lx
XMKDagwhGpv16I+wl97548APCdjj2XpanGNrnhZV3jKDZamQNCOaXfvGOA+86Zdh
bvlw5LqeST5oTiVzFbuLRmxiFu7BmBNrfhYNNAQPqgI+s0JKToFjgPUV6LCYwg/y
rUJxNu/bB8QOxvQ8D0/Qcw2M2JmQRxe6YCVoS8JjurDV6aMpXeNyLWYjjf5StIaA
C4bDmDAuaB2iuWTSNg2/
=BW6G
-----END PGP SIGNATURE-----
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2015-03-11  8:05 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 [this message]
2015-03-11  8:15               ` Anthony J. Bentley
2015-03-11 10:07               ` Steffen Nurpmeso
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=54FFF740.3080201@bsd.lv \
    --to=kristaps@bsd.lv \
    --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).