https://bugs.kde.org/show_bug.cgi?id=376789
--- Comment #4 from Massimo Burcheri <[email protected]> --- I had some old clients from 2007 that did not need P4CONFIG to be set, and the current from 2017 doesn't either. afaik the default always was to configure all in the environment: P4LOC P4CLIENT P4PORT P4USER Having a P4CONFIG and some file found this can overwrite these settings while superseeding with parent directories $P4CONFIG. So p4 on some /workspace/file would be different if your $PWD is $HOME or /workspace/file as that $P4CONFIG there could switch your $P4CLIENT. It could even switch your server $P4PORT. It's more a git way but we don't use it as things get more obfuscated by this. Anyway the perforce plugin should not rely on it. p4 will use the feature if configured. You could better add some local environment settings to set P4CLIENT per KDevelop project or just inherit the system environment. Look at qtcreator, they have some P4CLIENT and P4PORT settings in the dialog replacing the system environment settings. Usually on shell we switch the "project" by scripts exporting P4CLIENT to a subshell. While working in KDevelop don't have that option anymore so I would need to set these per project, but could also be done by the project generic environment settings of KDevelop. -- You are receiving this mail because: You are watching all bug changes.
