3 messages in com.perforce.perforce-userPCR options
FromSent OnAttachments
Robe...@perforce.com09 Jul 1997 11:23 
sjms...@xionics.com10 Jul 1997 08:18 
Matt...@geoworks.com10 Jul 1997 18:10 
Subject:PCR options
From:sjms...@xionics.com (sjms@xionics.com)
Date:07/10/1997 08:18:17 AM
List:com.perforce.perforce-user

My 2 cents:

Except when I am initially learning a system I read help/manuals etc. for one command at a time. I want to see all the relevent usage at that time. I don't care if it is redundant and I don't want to be forced to read other pages. Redundancy is a problem for the maintainer, not the user.

Robert Orenstein writes:

Yes. I've not yet figured out a way to handle this: one way is to list them in a separate section of their own, another way is to list them with each command, and a third way is to list them separately along with a note in EVERY command that says "Please see ... for options common to all commands". I'm not crazy about any of these methods. Any ideas?

These options of p4(1) are generic to all sub-commands...

OPTIONS -c client Set client workspace name (defaults $P4CLIENT, hostname)

-d directory Set current directrory path (default $PWD)

-p port Set connect port (default perforce:1666)

-u user Set user name (defaults $P4USER, $USERNAME, $USER)

-v x debug mode at level x.

-x file read command arguments, one per line, from file.