From: r at uzy.me (Pablo Rauzy)
Subject: Description for section and link for repos
Date: Thu, 05 Mar 2015 12:16:40 +0100 [thread overview]
Message-ID: <87ioefvhc3.fsf@uzy.me> (raw)
In-Reply-To: <20150305095739.GB1369@serenity.lan>
On 2015-03-05, John Keeping wrote:
> On Thu, Mar 05, 2015 at 10:51:09AM +0100, Pablo Rauzy wrote:
>> What I was looking for is the possibility to for instance make cgit
>> using a file called "description" in the directory that it makes a
>> section as description of that section.
>
> I don't think this has ever been supported.
>
> CGit doesn't generate any links to the section pages so I'm not sure
> much thought has gone into the formatting of those pages.
That's what I infered. But I'd like to have both the link and the
formatting. I'll think about it when I have time to.
>> FWIW, here is the filter I wrote to make link clickable in plaintext
>> READMEs: http://paste.fulltxt.net/LKdVjbHaY (it is quick and dirty, it
>> simply considers that anything between < and > and starting with "http"
>> is a link).
>
> Note that there is a collection of scripts in the "filters" directory
> that will handle Markdown, ReStructuredText and a variety of other
> formats.
Yes I saw that, thanks. But I prefer to keep things simple (I only have
plaintext and html readme) and fast as cgit already is :).
Thanks,
--
Pablo Rauzy.
http://pablo.rauzy.name/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20150305/1cbbe889/attachment.asc>
prev parent reply other threads:[~2015-03-05 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 8:22 r
2015-03-05 9:30 ` john
2015-03-05 9:51 ` r
2015-03-05 9:57 ` john
2015-03-05 11:16 ` r [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=87ioefvhc3.fsf@uzy.me \
--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).