From: whydoubt at gmail.com (Jeffrey Smith)
Subject: [PATCH 0/4] adding color to ui-blame
Date: Sun, 15 Oct 2017 12:04:17 -0500 [thread overview]
Message-ID: <CAPX7N=7hEM+ZMTmd+TO8aG9Ly-kaVmwRTtSnSKp0mJ5Qofsg8Q@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pQs3CKe9gDfokBq28F89EqsrhTibdevWT4wev6cmxF9g@mail.gmail.com>
That seems like it could be valuable work, but FWIW I have been working on
a different solution to adding syntax highlighting to the blame page. I
hope to have it ready (at least a prototype) in the next day or two.
On Oct 15, 2017 11:47 AM, "Jason A. Donenfeld" <Jason at zx2c4.com> wrote:
> Right, we may very well need a more capable model.
>
> One approach would be to get rid of all the exec stuff, and instead
> have plugins, that can register themselves in all sorts of places. A
> plugin would define a series of hooks and filters, which would be
> directly called at the right time. We'd expand the Lua stuff to
> support that, and then add Python support and all the other various
> languages one at a time.
>
> Would indeed be a big project, but potentially useful.
>
> Though I _do_ like the simplicity of the current situation quite a bit.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20171015/cf28205f/attachment.html>
next prev parent reply other threads:[~2017-10-15 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 14:17 Jason
2017-10-14 14:17 ` [PATCH 1/4] filter: add generic scafolding for temporarily disabling filter Jason
2017-10-14 14:17 ` [PATCH 2/4] filter: wire up exec_filter to enable function Jason
2017-10-14 14:17 ` [PATCH 3/4] filter: wire up lua_filter " Jason
2017-10-14 14:17 ` [PATCH 4/4] ui-blame: put source lines through filter Jason
2017-10-14 16:14 ` [PATCH 0/4] adding color to ui-blame john
2017-10-15 16:47 ` Jason
2017-10-15 17:04 ` whydoubt [this message]
2017-10-15 17:11 ` Jason
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='CAPX7N=7hEM+ZMTmd+TO8aG9Ly-kaVmwRTtSnSKp0mJ5Qofsg8Q@mail.gmail.com' \
--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).