From: list at eworm.de (Christian Hesse)
Subject: Table of Contents links using the format #link are not followed
Date: Fri, 13 Jul 2018 18:14:51 +0200 [thread overview]
Message-ID: <20180713181451.3c53649a@leda> (raw)
In-Reply-To: <CAKcFC3Y_vZ-mJAN2gGwPgjC6YYzhLbthCWK9D4=+1aqgjifAgA@mail.gmail.com>
jean-christophe manciot <actionmystique at gmail.com> on Fri, 2018/07/06 11:56:
> Ubuntu 18.10
> cgit commit 22583c4
> git 2.18.0-1
>
> For instance, the following table of contents successfully tested on gitlab
> is useless on cgit:
> ## Table of Contents
>
> + [Drive Repository Contents](#drive-repository-contents)
> + [Features](#features)
> ...
>
> ## Drive Repository Contents
>
> ...
>
> ## Features
>
> Clicking on one of the table of contents link should redirect the user to
> the corresponding paragraph, but it does not.
> Either I'm missing something, or that feature is not implemented (yet?), or
> there is some kind of issue.
The links are ok, but python-markdown does not add the anchors in links
(a-tags). Anybody familiar with python-markdown can tell if that can be
changed?
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20180713/7702327e/attachment.asc>
next prev parent reply other threads:[~2018-07-13 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 9:56 actionmystique
2018-07-13 16:14 ` list [this message]
2018-07-13 16:39 `
2018-07-13 19:48 ` [PATCH 1/1] filters: generate anchor links from markdown list
2018-08-25 9:45 ` john
2018-08-25 12:02 ` list
2018-08-25 17:11 ` Jason
2018-08-25 17:47 ` john
2018-08-26 0:01 ` Jason
2018-08-25 7:39 Table of Contents links using the format #link are not followed actionmystique
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=20180713181451.3c53649a@leda \
--to=cgit@lists.zx2c4.com \
/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).