Review Request: Make "Execute" automagically switch to an appropriate launch config based on its name

[Eike Hein]

> On Oct. 24, 2012, 11:59 a.m., Andreas Pakulat wrote:
> > How about also adding an "executable target" heuristic into the mix, i.e. if the current file is part of a single executable target and there's a launch config using that target, launch it?

Sounds reasonable :).


- Eike


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/107020/#review20786
-----------------------------------------------------------


On Oct. 24, 2012, 11:34 a.m., Eike Hein wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/107020/
> -----------------------------------------------------------
> 
> (Updated Oct. 24, 2012, 11:34 a.m.)
> 
> 
> Review request for KDevelop and Aleix Pol Gonzalez.
> 
> 
> Description
> -------
> 
> This patch aims to make the "Execute" action more convenient and useful by switching the active launch configuration at the time the action is invoked in one of the following ways:
> 
> - If any launch config name matches the start of the name of the currently viewed file, use that launch config.
> 
> - Failing the above, if any launch config name matches the name of the project owning the currently viewed file, use that launch config.
> 
> If neither succeeds, the launch config is unchanged.
> 
> Bottom line: If you have more than launch config for a single project, chances are you're launching individual scripts or executables inside the project and are naming your launch configs after those files. If you only have a single launch config per project - but more than one project in the session - chances are they'll be named after the projects. The behavior outlined succeeds in switching to the appropriate launch config in both cases.
> 
> Now, this behavior is 'magic' and, while useful, essentially unpredictable to the user. Personally I have trouble with seeing it in the mainline for that reason, and think it needs some sort of UI to control it. However, I have no non-convoluted idea for how that UI might look like, and Aleix succeeded in talking me into filing a review request anyway - if nothing else, maybe it'll get us somewhere in discussion.
> 
> 
> Diffs
> -----
> 
>   shell/runcontroller.cpp 0f0547e 
> 
> Diff: http://git.reviewboard.kde.org/r/107020/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Eike Hein
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20121024/19a689d9/attachment.html>