zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Nils Steinger <zsh-list@voidptr.de>
Cc: zsh-workers@zsh.org
Subject: Re: VCS_INFO_get_data_git produces output in git-annex directories
Date: Sat, 29 Mar 2014 09:54:37 +0000	[thread overview]
Message-ID: <20140329095437.GC11569@tarsus.local2> (raw)
In-Reply-To: <20140310183155.GB29473@voidptr.de>

Nils Steinger wrote on Mon, Mar 10, 2014 at 19:31:56 +0100:
> Hi,
> 
> I'm using oh-my-zsh and noticed that whenever I changed into a directory
> containing a git-annex repository, "fatal: This operation must be run in
> a work tree" appeared above my shell prompt.

Would it be a better fix to change the if's condition to include 'git
rev-parse --is-inside-work-tree'?  I'm not sure whether that would break
some other use-case, but avoiding a non-working case seems preferable to
swallowing errors silently.

Cheers,

Daniel

P.S.  This patch conflicts with the one I just sent.  The conflict is
trivial (my patch just reindents the line your patch changes), but if
both patches are applied then whoever applies the second one will run
into it.

> After unsuccessfully grep-ing the oh-my-zsh sources for a command that
> could cause this output, I 'set -x' and found that the error message was
> caused by line 119 in
> /usr/share/zsh/functions/VCS_Info/Backends/VCS_INFO_get_data_git.
> 
> I assume that's accidental (since it's useless and annoying) and have
> attached a patch to fix this behavior.
> 
> Nils

> --- /usr/share/zsh/functions/VCS_Info/Backends/VCS_INFO_get_data_git.old    2014-03-10 18:16:33.514629788 +0000
> +++ /usr/share/zsh/functions/VCS_Info/Backends/VCS_INFO_get_data_git    2014-03-10 18:15:54.919823850 +0000
> @@ -116,7 +116,7 @@
>     [[ "$(${vcs_comm[cmd]} rev-parse --is-inside-git-dir 2> /dev/null)" != 'true' ]] && \
>     ${vcs_comm[cmd]} rev-parse --quiet --verify HEAD &> /dev/null ; then
>      # Default: off - these are potentially expensive on big repositories
> -    ${vcs_comm[cmd]} diff --no-ext-diff --ignore-submodules --quiet --exit-code ||
> +    ${vcs_comm[cmd]} diff --no-ext-diff --ignore-submodules --quiet --exit-code &> /dev/null ||
>          gitunstaged=1
>      ${vcs_comm[cmd]} diff-index --cached --quiet --ignore-submodules HEAD 2> /dev/null
>      (( $? && $? != 128 )) && gitstaged=1
> 


      reply	other threads:[~2014-03-29  9:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 18:31 Nils Steinger
2014-03-29  9:54 ` Daniel Shahaf [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=20140329095437.GC11569@tarsus.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-list@voidptr.de \
    --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).