From: Eli Barzilay <eli@barzilay.org>
To: wmpalmer@gmail.com
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Johannes Sixt <j.sixt@viscovery.net>,
Jared Hance <jaredhance@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH v2] An alias that starts with "!!" runs in the current directory.
Date: Wed, 5 May 2010 18:33:09 -0400 [thread overview]
Message-ID: <19425.61989.608102.77250@winooski.ccs.neu.edu> (raw)
In-Reply-To: <1273098179.723.10.camel@dreddbeard>
On May 5, Will Palmer wrote:
> On Wed, 2010-05-05 at 17:31 -0400, Eli Barzilay wrote:
> > With "!"-prefixed shell aliases, the shell command not only gets
> > executed at the repository top level, but there is no way to know the
> > current directory of the original call. This adds "!!"-prefixed aliases
> > as a similar variant for "!"-prefixed ones, but the commands are
> > executed in the original directory instead of the top level.
> >
> > Signed-off-by: Eli Barzilay <eli@barzilay.org>
>
> Is there any precedent for the "!!" syntax? Something like ".!",
> "./!", or "!(.)" would make the intention more clear, I'd think, as
> well as leaving room for other extensions to be added later, and
> some explicit-opposite, like "/!", to complement it. (It's not like
> people are going around with binaries called "!", is it?)
[
The first time I saw the "!" syntax, it was slightly confusing to me
in that it's similar to various shells using "!" for history expansion
-- especially given that these things are popular with shell aliases
made it hard to remember.
An alternative character that wouldn't have confused me, and even
suggests shell commands is ";". So my preference would be for shell
aliases to start with it and to be invoked in the original working
directory, perhaps deprecating the "!" syntax.
But I'm new enough to be safely ignored... So this is all a
parenthetical comment...
]
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
next prev parent reply other threads:[~2010-05-05 22:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 0:25 [PATCH] Set GIT_PATHNAME_PREFIX with aliases Jared Hance
2010-05-05 0:51 ` Jeff King
2010-05-05 6:53 ` Johannes Sixt
2010-05-05 7:01 ` Jeff King
2010-05-05 7:52 ` Eli Barzilay
2010-05-05 16:07 ` Junio C Hamano
2010-05-05 20:28 ` [PATCH] An alias that starts with "!!" runs in the current directory Eli Barzilay
2010-05-05 20:52 ` [PATCH] An alias that starts with "!!" " Jared Hance
2010-05-05 20:58 ` Eli Barzilay
2010-05-05 21:00 ` Eli Barzilay
2010-05-05 21:24 ` Re-submitting patches Jonathan Nieder
2010-05-05 21:28 ` Eli Barzilay
2010-05-05 21:31 ` [PATCH v2] An alias that starts with "!!" runs in the current directory Eli Barzilay
2010-05-05 22:22 ` Will Palmer
2010-05-05 22:33 ` Eli Barzilay [this message]
2010-05-05 23:43 ` Junio C Hamano
2010-05-06 0:05 ` Adam Brewster
2010-05-06 6:21 ` Will Palmer
2010-05-06 6:26 ` Will Palmer
2010-05-06 6:36 ` Johannes Sixt
2010-05-06 7:02 ` Matthieu Moy
2010-05-05 22:02 ` [PATCH] " Junio C Hamano
2010-05-05 22:13 ` Eli Barzilay
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=19425.61989.608102.77250@winooski.ccs.neu.edu \
--to=eli@barzilay.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=jaredhance@gmail.com \
--cc=peff@peff.net \
--cc=wmpalmer@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).