zsh-workers
 help / color / mirror / code / Atom feed
From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: Peter Stephenson <pws@csr.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: Minor VCS Info things
Date: Tue, 23 Sep 2008 12:15:21 -0700	[thread overview]
Message-ID: <20080923191520.GA65214@redoubt.spodhuis.org> (raw)
In-Reply-To: <20080923170245.4da323c0@news01>

On 2008-09-23 at 17:02 +0100, Peter Stephenson wrote:
> I've done this.  It seems to work OK.

As a side note: there's a scenario I have at $work where use-server
won't work but the simple case will: multiple P4 servers and the file
named by $P4CONFIG, in the root directory of the client, setting P4PORT
to the correct server.

I don't know of a way to deal with this for the use-server case, since
environment variables can't be auto-set by directory (although I could
use precmd() to mangle that in, just for this, I suppose).

So ...

> Index: Doc/Zsh/contrib.yo
[...]
> +until it is removed by hand.  If you do not set this style, the tt(p4)
> +backend is only usable if you have set the environment variable
> +tt(P4CONFIG) to a file name and have corresponding files in the root
> +directories of each Perforce client.  See comments in the function
> +tt(VCS_INFO_detect_p4) for more detail.

Suggest adding before the "See comments[...]" sentence:

  Using the tt(P4CONFIG) method may function better in environments with
  multiple P4 servers where tt(P4PORT) is set in the file named by
  tt(P4CONFIG).

-Phil


  reply	other threads:[~2008-09-23 19:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 14:11 Peter Stephenson
2008-09-22 16:48 ` Frank Terbeck
2008-09-22 23:43 ` Phil Pennock
2008-09-23 16:02 ` Peter Stephenson
2008-09-23 19:15   ` Phil Pennock [this message]
2008-09-24  8:46     ` Peter Stephenson
2008-09-24  9:08       ` Phil Pennock

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=20080923191520.GA65214@redoubt.spodhuis.org \
    --to=zsh-workers+phil.pennock@spodhuis.org \
    --cc=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /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).