tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: "Anthony J. Bentley" <anthony@anjbe.name>
Cc: tech@mdocml.bsd.lv
Subject: Re: -Tmarkdown: don't wrap mailtos in <>
Date: Thu, 9 Mar 2017 03:32:35 +0100	[thread overview]
Message-ID: <20170309023235.GA76398@athene.usta.de> (raw)
In-Reply-To: <34636.1489024072@cathet.us>

Hi Anthony,

Anthony J. Bentley wrote on Wed, Mar 08, 2017 at 06:47:52PM -0700:

> Currently -Tmarkdown wraps Mt email addresses in <>.

Yes, and that is indeed required.  That is markdown syntax
which will be tranformed into <a href="mailto:...>...</a>
by the markdown compiler.  Contrary to the outward appearance,
the angle brackets are *not* duplicate.

Your diff is very wrong and completely breaks .Mt hyperlinking.

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2017-03-09  2:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09  1:47 Anthony J. Bentley
2017-03-09  2:32 ` Ingo Schwarze [this message]
2017-03-09  7:27   ` Anthony J. Bentley
2017-03-09 16:39     ` Ingo Schwarze

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=20170309023235.GA76398@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=anthony@anjbe.name \
    --cc=tech@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).