You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Install newest P4V
2. Note that commands like "history" no longer work
What is the expected output? What do you see instead?
Expected: P4V opens history, revision graph etc.
Actual: P4V pops up an error dialog
What version of the product are you using? On what operating system?
Rev. Perforce Visual Client/NTX64/2013.1/611291
NiftyPerforce 1.4
Please provide any additional information below.
List of valid commands:
C:\Program Files\Perforce>p4vc help
help Print the requested help message
branchmappings Shows list of branch mappings
branches Same as branchmappings. Shows list of branch mappings
diff Shows diff dialog
groups Shows list of groups
branch Show/Edit branch
change Show/Edit change
client Same as workspace. Show/Edit workspace
workspace Show/Edit workspace
depot Show/Edit depot
group Show/Edit group
job Show/Edit job
label Show/Edit label
user Show/Edit user
jobs Shows list of jobs
labels Shows list of labels
pendingchanges Shows list of pending changes
resolve Launches resolve dialog
revisiongraph Shows revision graph
revgraph Same as revisiongraph. Shows revision graph
streamgraph Shows stream graph pane
streams Shows list of streams
submit Launches submit dialog
submittedchanges Shows list of submitted changes
timelapse Shows timelapse view
timelapseview Same as timelapse. Shows timelapse view
tlv Same as timelapse. Shows timelapse view
users Shows list of users
workspaces Shows list of workspaces
clients Same as workspaces. Shows list of workspaces
shutdown Shut downs the p4v service
I don't think it should be hard to fix this. For instance, instead of "p4v
-cmd history" nifty should pass "p4v -cmd submittedchanges."
Original issue reported on code.google.com by [email protected] on 19 Aug 2013 at 3:18
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 19 Aug 2013 at 3:18The text was updated successfully, but these errors were encountered: