From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH 0/3] git log --pretty=lua
Date: Sun, 30 Sep 2012 11:31:13 +0700 [thread overview]
Message-ID: <CACsJy8AvC9=6owwzMByZq2Wv1P_YS5xCUXRHH_Lr4qHA1BXyRQ@mail.gmail.com> (raw)
In-Reply-To: <20120925002325.GA19560@sigill.intra.peff.net>
On Tue, Sep 25, 2012 at 7:23 AM, Jeff King <peff@peff.net> wrote:
> Why Lua? I don't especially like it as a language. But it's designed for
> this purpose, which makes it very lightweight and relatively simple to
> embed.
Another option is tcl. String-based approach feels more natural for
pretty.c and shell users. >=8.1 supports utf-8. We might be able to
share some routines between the embedded tcl interpreter and
gitk/git-gui. The drawback is we won't get the speed of luajit if we
ever need to (I'm looking at filter-branch, but I assume eliminating
fork() should already give decent speedup).
--
Duy
prev parent reply other threads:[~2012-09-30 4:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 0:23 [RFC/PATCH 0/3] git log --pretty=lua Jeff King
2012-09-25 0:24 ` [PATCH 1/3] pretty: make some commit-parsing helpers more public Jeff King
2012-09-25 0:25 ` [PATCH 2/3] add basic lua infrastructure Jeff King
2012-09-25 1:55 ` Nguyen Thai Ngoc Duy
2012-09-25 4:53 ` Jeff King
2012-09-25 3:21 ` Robin H. Johnson
2012-09-25 3:42 ` Jeff King
2012-09-25 21:18 ` Junio C Hamano
2012-09-25 0:25 ` [PATCH 3/3] add a "lua" pretty format Jeff King
2012-10-06 17:33 ` Jeff King
2012-09-25 11:22 ` [RFC/PATCH 0/3] git log --pretty=lua Nguyen Thai Ngoc Duy
2012-09-25 13:49 ` Stephen Bash
2012-09-25 15:19 ` Matthieu Moy
2012-09-25 16:40 ` Junio C Hamano
2012-09-30 4:31 ` Nguyen Thai Ngoc Duy [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8AvC9=6owwzMByZq2Wv1P_YS5xCUXRHH_Lr4qHA1BXyRQ@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).