Bug 312883

Summary: No "new session" in the kdevelop sessions widget
Product: [Unmaintained] plasma4 Reporter: Michael Daffin <james1479>
Component: widget-miscAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: wishlist CC: ab4bd, aleixpol
Priority: NOR    
Version: 4.9.97 RC2   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Michael Daffin 2013-01-08 13:57:25 UTC
There is no way to launch a new session of kdevelop from the kdevelop sessions widget. It would be handy to be able to do this from the widget without having to have another icon to do this.

All that is required is to add another entry to the list called "New Session" that launches kdevelop with a new session rather then starting an existing session.

Reproducible: Always
Comment 1 George L. Emigh 2013-12-07 21:19:36 UTC
The Kate Sessions applet (widget) has the feature.

It would really be nice if the Kdevelop Sessions applet (widget) had the same features as the Kate Sessions applet (widget)

And opened to the same size, font, etc as the Kate Sessions applet (widget)

Thank you
Comment 2 Aleix Pol 2014-03-15 19:07:56 UTC
That would indeed be interesting, we don't have anybody working on that plasmoid at the moment. We would really appreciate if somebody could take a look into this.
Comment 3 Nate Graham 2018-06-08 20:11:10 UTC
Hello!

This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable.

Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham