public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Pablo Rodríguez" <oinos-S0/GAf8tV78@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: help filtering links
Date: Mon, 13 Mar 2023 17:21:29 +0100	[thread overview]
Message-ID: <3f0291e2-f077-1538-c1f5-104e4582733b@web.de> (raw)
In-Reply-To: <874jqo7j27.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>

On 3/13/23 16:40, Albert Krewinkel wrote:
> [...]
> You're right of course, I forgot that CommonMark behaves differently.
> Typically, only autolinks have a link text that's the same as the link,
> so we can check for that:
>
>     local function add_classes (link)
>       local id = link.target:match '^%#(.*)'
>       if id and headers[id] then
>         link.classes:insert 'section-link'
>       elseif link.target == pandoc.utils.stringify(link.content) then
>         link.classes:insert 'auto-link'
>       end
>       return link
>     end

Many thanks for your help, Albert.

I also used your filter (attributing your authorship) to close an old issue.

Many thanks again,

Pablo


      parent reply	other threads:[~2023-03-13 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 18:07 Pablo Rodríguez
     [not found] ` <b5007e61-547d-7661-530b-a3ef6ef19b20-S0/GAf8tV78@public.gmane.org>
2023-03-12 20:36   ` AW: " denis.maier-NSENcxR/0n0
2023-03-13 13:13   ` Albert Krewinkel
     [not found]     ` <878rg07pwn.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-03-13 15:19       ` Pablo Rodríguez
     [not found]         ` <c55f1066-db3d-aa64-b90f-36f7050ad2ed-S0/GAf8tV78@public.gmane.org>
2023-03-13 15:40           ` Albert Krewinkel
     [not found]             ` <874jqo7j27.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-03-13 16:21               ` Pablo Rodríguez [this message]

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=3f0291e2-f077-1538-c1f5-104e4582733b@web.de \
    --to=oinos-s0/gaf8tv78@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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).