zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Hahler <dhahler@gmail.com>
To: zsh-workers@zsh.org
Subject: BUG: failure in "vcs_info prompt" aborts precmd function
Date: Sat, 22 Nov 2014 18:13:11 +0100	[thread overview]
Message-ID: <5470C427.4050805@thequod.de> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I am using a precmd hook to setup my prompt and call "vcs_info 'prompt'" from there.

When starting an interactive Git rebase, while the editor is still open, it will fail as follows:

    VCS_INFO_get_data_git:208: no such file or directory: .git/rebase-merge/done

While this bug can be fixed (I'll post a patch), I think it's still a bug that vcs_info aborts the precmd.

Why is that?

I have tried adding "set +e" and "|| true" before the call to vcs_info, but without success.


Regards,
Daniel.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iD8DBQFUcMQnfAK/hT/mPgARAg43AJ9e2H/SW5RlRu0HkN2xfrdJITLG7QCgtTIo
uWKxYeqH7EheJ0wMB30xsrg=
=BdkI
-----END PGP SIGNATURE-----


             reply	other threads:[~2014-11-22 17:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-22 17:13 Daniel Hahler [this message]
2014-11-22 17:20 ` [PATCH] vcs_info: test -f .git/rebase-merge/done before reading it Daniel Hahler
2014-11-22 17:51 ` BUG: failure in "vcs_info prompt" aborts precmd function Mikael Magnusson
2014-11-22 18:01   ` Daniel Hahler
2014-11-22 22:20     ` Mikael Magnusson
2014-11-22 22:44       ` Bart Schaefer
2014-11-23 19:02         ` Peter Stephenson
2014-11-23 19:38           ` Bart Schaefer
2014-11-23 20:04             ` Peter Stephenson
2014-11-23 15:58       ` Daniel Hahler
2014-11-23 18:08         ` Mikael Magnusson
2014-11-23 19:57           ` TRY_BLOCK_ERROR and exit status Bart Schaefer
2014-11-24 10:11             ` Peter Stephenson
2014-11-25  8:01               ` Bart Schaefer
2014-11-25  9:18                 ` Peter Stephenson
2014-11-23 18:13         ` BUG: failure in "vcs_info prompt" aborts precmd function Bart Schaefer
2014-11-23 18:52           ` Mikael Magnusson
2014-11-23 19:47             ` Bart Schaefer
2014-11-23 22:03           ` Oliver Kiddle

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=5470C427.4050805@thequod.de \
    --to=dhahler@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).