From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH 1/4] git-sh-i18n--envsubst: our own envsubst(1) for eval_gettext()
Date: Mon, 9 May 2011 09:52:09 +0200 [thread overview]
Message-ID: <BANLkTino5PpXY8eD+T3Ki+2Xn1MLjZojTQ@mail.gmail.com> (raw)
In-Reply-To: <7vsjsor29t.fsf@alter.siamese.dyndns.org>
On Mon, May 9, 2011 at 05:17, Junio C Hamano <gitster@pobox.com> wrote:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> Or are we sure that this can't work in POSIX (or non-POSIX shells)?
>
> You need to implement the same logic to tokenize enough to understand the
> expansion the shell does inside dq. Yes, shell is general programming
> language and you can theoretically implement it, but would the result be a
> practical solution? I doubt it.
I'll write a better commit message and re-send this soon (after some
other comments have trickled in).
next prev parent reply other threads:[~2011-05-09 7:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 12:10 [PATCH 0/4] i18n: Add shell script translation infrastructure Ævar Arnfjörð Bjarmason
2011-05-08 12:10 ` [PATCH 1/4] git-sh-i18n--envsubst: our own envsubst(1) for eval_gettext() Ævar Arnfjörð Bjarmason
2011-05-08 17:15 ` Junio C Hamano
2011-05-08 21:33 ` Ævar Arnfjörð Bjarmason
2011-05-09 3:17 ` Junio C Hamano
2011-05-09 7:52 ` Ævar Arnfjörð Bjarmason [this message]
2011-05-08 12:10 ` [PATCH 2/4] git-sh-i18n.sh: add no-op gettext() and eval_gettext() wrappers Ævar Arnfjörð Bjarmason
2011-05-08 12:10 ` [PATCH 3/4] git-sh-i18n.sh: add GIT_GETTEXT_POISON support Ævar Arnfjörð Bjarmason
2011-05-08 12:10 ` [PATCH 4/4] Makefile: add xgettext target for *.sh files Ævar Arnfjörð Bjarmason
2011-05-08 17:03 ` [PATCH 0/4] i18n: Add shell script translation infrastructure Sverre Rabbelier
2011-05-08 21:38 ` Ævar Arnfjörð Bjarmason
2011-05-08 21:45 ` Sverre Rabbelier
2011-05-08 21:52 ` Ævar Arnfjörð Bjarmason
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=BANLkTino5PpXY8eD+T3Ki+2Xn1MLjZojTQ@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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).