From: Frank Terbeck <ft@bewatermyfriend.org>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: Minor VCS Info things
Date: Mon, 22 Sep 2008 18:48:23 +0200 [thread overview]
Message-ID: <20080922164823.GE11090@fsst.voodoo.lan> (raw)
In-Reply-To: <15055.1222092662@csr.com>
Peter Stephenson <pws@csr.com>:
> Some minor changes for VCS_Info I'd like to suggest, if they're
> uncontroversial.
[...]
I think all of these suggestions are the right thing to do.
> The Perforce detector doesn't work very well. $P4CONFIG is not tied to
> being in the Perforce workspace: you can have a config file outside a
> workspace to set a default client etc., and you don't need one at all if
> the client etc. are set via environment variables. The only good way of
> detecting whether you're in a workspace is to ask the server.
> Unfortunately this can hang (though not permanently) if the server is
> not available, so I haven't sent a patch. It could be fixed by adding
> an explicit style to use the server and also a global (per server:port
> pair) flag that the server didn't respond, so that it only hangs (for a
> second or two) the first time.
I'm not familiar with perforce myself. I think it's safe to trust
people who actually use a system. The explicit style idea sounds nice
enough.
Whatever works for perforce users, we should do.
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2008-09-22 16:49 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 [this message]
2008-09-22 23:43 ` Phil Pennock
2008-09-23 16:02 ` Peter Stephenson
2008-09-23 19:15 ` Phil Pennock
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=20080922164823.GE11090@fsst.voodoo.lan \
--to=ft@bewatermyfriend.org \
--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).