On Wed, 24 Feb 2016 20:10:09 -0800 (PST)
hiroki yasui <[email protected]> wrote:
> I ofter use the below command
> $git commit -am "something message"
>
> After setting alias, unfortunately that'd not work well.
>
> .gitconfig file is
> [alias]
> am = "!f(){ git commit -am \"$1\";};f"
>
> And then I tried,
> $ git am "modified something logic"
>
> something error occurred.
>
> fatal: could not open 'filepath//modified something logic: No such
> file or
> > directory
>
> What is wrong to set alias??
Two problems:
1) `git am` is a legitimate extsting Git command which applies
a patch series from a file (mbox-style) so I'd use some other
mnemonic even though this one appears to be compelling.
2) You're over-complicating the solution by deferring to the shell
while you don't have to: with "simple" aliases, all the arguments
are appended to the expanded alias as you would expect it,
so:
% git config --local --add alias.xx 'commit -a -m'
% git xx 'hey!'
[master (root-commit) 1a73bc8] hey!
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 foo
That is, when called, my "xx" alias is expanded to
"git" + alias text + any user-supplied arguments
producing:
git commit -a -m 'Hey!'
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
