From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Multi-word aliases?
Date: Tue, 4 Nov 2014 12:33:05 +0100 [thread overview]
Message-ID: <20141104113305.GA13232@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAHYJk3T9P_dwgkm+rG==828Sjqgbv+v4P0m0QdZtudG=3T+Gig@mail.gmail.com>
On Tue, Nov 04, 2014 at 11:59:09AM +0100, Mikael Magnusson wrote:
> On Tue, Nov 4, 2014 at 11:43 AM, Dominik Vogt <vogt@linux.vnet.ibm.com> wrote:
> > According to the man page, you can only define new aliases, not
> > overwrite subcommands.
> >
> > $ man git-config
> > ...
> > To avoid confusion and troubles with script usage, aliases that
> > hide existing git commands are ignored.
>
> Is there a strong reason you don't want to write "git rk" or whatever
> at the command line?
Yes: I don't want to create my own syntax that nobody understands
but me and then be unable to work on a plain system without silly
"custom" configuration. I tried it but found the mechanism
awkward and confusing - and the colleagues did not understand what
I was doing.
> I'm quite lazy with typing so I have a set of
> aliases like git rc, git rs for --continue, --skip, and git amend for
> git commit --amend.
I have some handy shell aliases for some lengthy commands that
nobody else would ever use, but I wouldn't bother bother to do
that in an application specific way. I don't really mind the
typing (because it's usually just "git reb<Up><Up><Return>".
What's really annoying is that rebase silently dumps empty commits
without that option (I use empty commits with comments like "--
ready-to-submit --" or "-- submitted --" in my work repo to sort
patches).
> As for the global command line regex replace, yes, you can do that if
> you hook into the accept-line family of widgets but there's a huge
> caveat; it will only do literal replacements (obviously), so if you
> want to respect any form of quoting you'll have to reimplement the
> full zsh parser in shell script
Ouch!
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
next prev parent reply other threads:[~2014-11-04 11:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 9:08 Dominik Vogt
2014-11-04 9:56 ` Peter Stephenson
2014-11-04 10:43 ` Dominik Vogt
2014-11-04 10:59 ` Mikael Magnusson
2014-11-04 11:33 ` Dominik Vogt [this message]
2014-11-04 12:32 ` Mikael Magnusson
2014-11-04 12:39 ` Peter Stephenson
2014-11-04 12:53 ` Dominik Vogt
2014-11-04 15:57 ` Vincent Lefevre
2014-11-04 11:32 ` Peter Stephenson
[not found] <20141104090838.GA27526__23771.1416128606$1415092256$gmane$org@linux.vnet.ibm.com>
2014-11-04 10:20 ` Stephane Chazelas
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=20141104113305.GA13232@linux.vnet.ibm.com \
--to=vogt@linux.vnet.ibm.com \
--cc=zsh-users@zsh.org \
/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://git.vuxu.org/mirror/zsh/
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).