With the last change to the perforce plugin I am now seeing Could not load plugin "kdevperforce" , it reported the error: "The variable P4CONFIG is not set." Disabling the plugin now. each time I open a session I hadn't opened since the last updated. IMHO this is indicative of an underlying issue with the settings management: it isn't clear which apply per session and which apply globally. It thus cannot be clear either what settings are session-specific overrides of a global default. I don't use perforce, so don't have any reason to set P4CONFIG, and also do not need to be reminded of that every time I create a new session. The perforce plugin can be disabled once and for all (either automatically or manually), and then that setting can apply to all sessions (present, past and future). Reproducible: Always Steps to Reproduce: 1. update to KDevPlatform 4.90.91.370 or later 2. create a new session or open an existing session not yet upgraded Actual Results: Could not load plugin "kdevperforce" , it reported the error: "The variable P4CONFIG is not set." Disabling the plugin now. Expected Results: The above error should be printed at most once, the 1st time the absence of P4CONFIG is detected
This btw. sounds like a bug in the perforce plugin. Like the cmake or git plugins, it should simply disable itself if it cannot find the required external binary. And it should do that without showing a message dialog.
There's that too of course. It's not the plugin that prints the message though (I don't get a dialog). It just sets an error message and returns an error code; the message is printed at a higher level like a plugin manager.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!