zsh-workers
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: Valni <ttemplate223@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: Call git directly to bypass possible functions under the same name
Date: Thu, 04 Feb 2016 22:19:05 +0100	[thread overview]
Message-ID: <878u30jhrq.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <56B3BBEE.3030309@gmail.com> (Valni's message of "Thu, 4 Feb 2016 22:00:30 +0100")

Valni wrote:
> Hopefully I have reached the right mailing list and posted a valid
> question/issue.

This would probably be better suited on the zsh-users list, but you're
in the right vicinity. :)

> ---
>
> I stumbled upon an issue today when creating a function which adds SSH
> keys to an agent on demand. This function should (and does, in `zsh -f`)
> only be called when git/ssh is used. The function also has the same name
> as the program.
>
> However, I use a zsh framework which depends on vcs_info, which causes
> some issue (https://github.com/Eriner/zim/issues/30).
>
> When git is called from vcs_info, it does not appear to call it
> directly, so any definitions of it, such as a function, will take priority.
>
> This results in the function (seen in the first post of the GitHub
> issue) being called when any (or none at all) command is called, because
> the framework checks if the current directory is used by git using vcs_info.
>
> Could vcs_info be changed so that it calls git directly? Thus far, this
> appears to be the cause of the issue.

We are not going to change the way that vcs_info works with respect to
this. If you got a wrapper that is incompatible with the way that git
works, use a "command" style to force the command used by vcs_info to
its full path name:

   % zstyle ':vcs_info:git:*:-all-' command =git


Regards, Frank


      reply	other threads:[~2016-02-04 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 21:00 Valni
2016-02-04 21:19 ` Frank Terbeck [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878u30jhrq.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --cc=ttemplate223@gmail.com \
    --cc=zsh-workers@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).