From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-users@zsh.org
Subject: vcs_info git quilt: gen-applied-string hook
Date: Thu, 22 Oct 2015 12:31:38 +0000 [thread overview]
Message-ID: <20151022123138.GH7173@tarsus.local2> (raw)
$ zsh -f
% autoload -Uz vcs_info
% precmd() { vcs_info ; print -rl - $vcs_info_msg_0_ $vcs_info_msg_1_ $vcs_info_msg_2_ }
% zstyle :vcs_info:\* use-quilt true
% zstyle :vcs_info:\* actionformats %m
% zstyle :vcs_info:\* formats %Q
% zstyle :vcs_info:git+gen-applied-string:\* hooks f
% +vi-f() { hook_com[applied-string]="+vi-f: Called with ${(q-)1}"; ret=1 }
The above hook gets called both by the git backend (e.g., during a rebase) and
by the 'addon' quilt mode.
I can discriminate the two cases via (( $+funcstack[(r)VCS_INFO_quilt] )).
My question is just whether the hook should be called by 'addon' quilt
mode in the first place. Should quilt mode look up hooks under the
context :vcs_info:git.quilt-addon+gen-applied-string:* instead?
^^^^^^^^^^^^
Cheers,
Daniel
reply other threads:[~2015-10-22 12:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20151022123138.GH7173@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--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).