public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: dev.crst-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Cc: nick-iTLVOByc1N8@public.gmane.org
Subject: Re: Header self-links gone?
Date: Wed, 23 Nov 2016 02:51:52 -0800 (PST)	[thread overview]
Message-ID: <ac25089d-f112-4795-8524-ac705b521fcc@googlegroups.com> (raw)
In-Reply-To: <20150227141002.GI5930-iTLVOByc1N8@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1967 bytes --]

Nick Moffitt:
>
>     1: It used to be that with section-divs and toc, I'd still get 
>        self-links on section headers.  So like: 
>
>         ## Foo 
>        would make 
>         <h2><a href="#foo">Foo</a></h2> 
>

 A few days ago I upgraded Linux Mint and was also wondering why this 
"Self-Link" feature wasn't working anymore. After some naive investigation 
I found the answer in the changelog <http://pandoc.org/changelog.txt> down 
at "pandoc (1.12.3)":

  * HTML writer:

    + With `--toc`, headers no longer link to themselves (#1081).

At #1081 <https://github.com/jgm/pandoc/issues/1081> there is the reason 
for this.

I also missed this feature and my workaround I can live with is a little 
javascript in the html-template's header:

<script>
    function headerLink() {
        for (var level = 1; level <= 6; level++) {
            var header = document.getElementsByTagName("h" + level);
            var i;
            for (i = 0; i < header.length; i++) {
                header[i].innerHTML =
                    '<a href="#'
                    + header[i].id
                    + '">'
                    + header[i].innerHTML + '</a>';
            }
        }
    }
</script>

Now just change
<body>
to
<body onload="headerLink()">

is there some extension I can turn on to get that back?
>

Yeah that'd be *great* <https://memegenerator.net/Yeah-ThatD-Be-Great>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ac25089d-f112-4795-8524-ac705b521fcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 11733 bytes --]

  parent reply	other threads:[~2016-11-23 10:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 14:10 Nick Moffitt
     [not found] ` <20150227141002.GI5930-iTLVOByc1N8@public.gmane.org>
2015-03-03 18:53   ` John MacFarlane
     [not found]     ` <20150303185309.GH52906-0VdLhd/A9Pm0ooXD8Eul3coeWC+rr2vXTVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
2015-03-04  8:07       ` Nick Moffitt
2016-11-23 10:51   ` dev.crst-Re5JQEeQqe8AvxtiuMwx3w [this message]
     [not found]     ` <ac25089d-f112-4795-8524-ac705b521fcc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-11-23 11:22       ` Nick Moffitt
     [not found]         ` <20161123112238.GA8136-iTLVOByc1N8@public.gmane.org>
2016-11-23 23:24           ` BP Jonsson
     [not found]             ` <4ab21d15-9697-c060-61fb-96c32ce41f6e-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-11-24 10:43               ` Christoph Strasser
     [not found]                 ` <bb4ed5a7-c81e-420b-bdc6-74a3b675a653-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-11-25 21:10                   ` Christoph Strasser
     [not found]                     ` <6049b086-bbeb-642c-2b42-55b38e8d107e-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-11-26 11:25                       ` BP Jonsson
2016-11-23 13:00       ` John MacFarlane
     [not found]         ` <20161123130026.GA88680-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org>
2016-11-23 13:53           ` Christoph Strasser

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=ac25089d-f112-4795-8524-ac705b521fcc@googlegroups.com \
    --to=dev.crst-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=nick-iTLVOByc1N8@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).