{"id":4572,"date":"2018-01-09T06:17:30","date_gmt":"2018-01-09T06:17:30","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/?p=4572"},"modified":"2025-02-01T22:39:32","modified_gmt":"2025-02-01T22:39:32","slug":"perforce-command-line-global-options","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/perforce-command-line-global-options\/","title":{"rendered":"Perforce Command Line Global Options"},"content":{"rendered":"

<!– .style1 { font-size: 24px; font-weight: bold; } –><\/p>\n

Perforce Command Line Global Options<\/strong><\/p>\n

<\/a>Global options for Perforce commands; these options can be supplied on the command\u00a0line before any Perforce command.<\/p>\n

<\/a>Syntax<\/strong><\/div>\n
<\/a>p4 [-cclient -ddir -Hhost -pport -Ppass -uuser -xfile -Ccharset -Qcharset -Llanguage] [-G] [-s] [-z tag] cmd [args …]
\np4 -V
\np4 -h<\/div>\n

 <\/p>\n

<\/a>Options<\/strong><\/div>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\u00a0<\/caption>\n
\n\n
\n\n
\n\n
\n\n
\n\n
\n\n
\n\n
\n\n
\n\n
\n\n
\n\n
\n\n
\n\n
\n\n
\n\n
<\/a>Displays basic usage information and exits.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

<\/a>Usage Notes<\/strong><\/div>\n
\n\n\n\n
\n
\u2022<\/div>\n<\/td>\n
\n
<\/a>Be aware that the global options must be specified on the command line before the\u00a0Perforce command. Options specified after the Perforce command will not be interpreted as global options, but as options for the command being invoked. It is therefore possible to have the same command line option appearing twice in the same command, being interpreted differently each time.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
<\/a>For example, the command\u00a0p4 -c anotherclient edit -c 140 file.c will open file file.c for edit in pending changelist 140 under client workspace anotherclient.<\/div>\n
\n\n\n\n
\n
\u2022<\/div>\n<\/td>\n
\n
<\/a>The\u00a0-x option is useful for automating tedious tasks; a user adding several files at once could create a text file with the names of these files and invoke p4 -x textfile add to add them all at once.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
<\/a>The\u00a0-x option can be extremely powerful – as powerful as whatever generates its input. For example, a UNIX developer wishing to edit any file referring to an included file.h file, for instance, could grep -l file.h *.c | cut -f1 -d: | p4 -x – edit.<\/div>\n
<\/a>In this example, the\u00a0grep command lists occurrences of file.h in the *.c files, the -l option tells grep to list each file only once, and the cut command splits off the filename from grep’s output before passing it to the p4 -x command.<\/div>\n
\n\n\n\n
\n
\u2022<\/div>\n<\/td>\n
\n
<\/a>The\u00a0-s option can be useful in automated scripts.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
<\/a>For example, a script could be written as part of an in-house build process which\u00a0executes p4 -s commands, discards any output lines beginning with “info:”, and alerts the user if any output lines begin with “error:”.<\/div>\n
\n\n\n\n
\n
\u2022<\/div>\n<\/td>\n
\n
<\/a>Python developers will find the\u00a0-G option extremely useful for scripting. For instance, to get a dictionary of all fields of a job whose ID is known, use the following:<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
<\/a>job_dict = marshal.load(os.popen(‘p4 -G job -o ‘ + job_id, ‘rb’))<\/div>\n
<\/a>In some cases, it may not be intuitively obvious what keys are used by the client\u00a0program. If you pipe the output of any p4 -G invocation to the following script, you will see every record printed out in key\/value pairs:<\/div>\n","protected":false},"excerpt":{"rendered":"

<!– .style1 { font-size: 24px; font-weight: bold; } –> Perforce Command Line Global Options Global options for Perforce commands; these options can be supplied on the command\u00a0line before any Perforce command. Syntax p4 [-cclient -ddir -Hhost -pport -Ppass -uuser -xfile -Ccharset -Qcharset -Llanguage] [-G] [-s] [-z tag] cmd [args …] p4 -V p4 -h  …<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_joinchat":[],"footnotes":""},"categories":[370],"tags":[824,1961,373,4491,3204,3214],"class_list":["post-4572","post","type-post","status-publish","format-standard","hentry","category-perforce","tag-command-line","tag-p4-command-line","tag-perforce","tag-perforce-command-line-cheatsheet","tag-perforce-command-line","tag-perforce-command-line-reference"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/4572","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=4572"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/4572\/revisions"}],"predecessor-version":[{"id":4573,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/4572\/revisions\/4573"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=4572"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=4572"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=4572"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}