zsh-workers
 help / color / mirror / code / Atom feed
From: Aaron Schrab <aaron@schrab.com>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: Daniel Shahaf <d.s@daniel.shahaf.name>,
	zsh-workers@zsh.org, Bart Schaefer <schaefer@brasslantern.com>,
	Manfred Lotz <manfred.lotz@arcor.de>
Subject: Re:  vcs_info: Use ‘command’ prefix to call version control programs
Date: Wed, 22 Oct 2014 08:42:56 -0400	[thread overview]
Message-ID: <20141022124256.GA615@pug.qqx.org> (raw)
In-Reply-To: <87h9ywb9by.fsf@ft.bewatermyfriend.org>

At 14:03 +0200 22 Oct 2014, Frank Terbeck <ft@bewatermyfriend.org> wrote:
>That style could also be used to switch to a different binary, 
>depending on the current working copy. That's kind of what that style 
>was introduced for.

But somebody using a wrapper for that would likely want it to be used 
for things other than vcs_info, and the style wouldn't help there.

>About resolving this issue, I'm fine either way. I think Daniel has a
>point about setting the ‘command’ style, if you're using a wrapper
>function that's incompatible with the usual behaviour of a backend's
>external program.

Setting the command style would also work if the problematic wrapper is 
implemented as a stand-alone executable rather than as a shell function; 
using the `command` prefix only helps with incompatible functions.


  reply	other threads:[~2014-10-22 12:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22  4:24 VCS_INFO_get_data_svn:31: bad set of key/value pairs for associative array Manfred Lotz
2014-10-22  6:22 ` Bart Schaefer
2014-10-22  9:28   ` [PATCH] vcs_info: Use ‘command’ prefix to call version control programs Frank Terbeck
2014-10-22 10:53     ` Daniel Shahaf
2014-10-22 12:03       ` Frank Terbeck
2014-10-22 12:42         ` Aaron Schrab [this message]
2014-10-22 13:43           ` Frank Terbeck
2014-10-22 12:54         ` [PATCH] " Manfred Lotz
2014-10-22 13:51           ` Frank Terbeck

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=20141022124256.GA615@pug.qqx.org \
    --to=aaron@schrab.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=ft@bewatermyfriend.org \
    --cc=manfred.lotz@arcor.de \
    --cc=schaefer@brasslantern.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).