Bug 325262

Summary: Quoting for project names (and mapping to alternative identifiers?)
Product: [Applications] kdevelop Reporter: Markus Elfring <Markus.Elfring>
Component: Application templatesAssignee: kdevelop-bugs-null
Status: REPORTED ---    
Severity: normal CC: igorkuo
Priority: NOR    
Version First Reported In: 4.5.1   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
URL: https://projects.kde.org/projects/extragear/kdevelop/kdevelop/repository/revisions/041205ff7497c39ebffbb06a996395d8dc88ee67/entry/app_templates/cpp/CMake/cmake_plaincpp/CMakeLists.txt
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Markus Elfring 2013-09-24 17:15:46 UTC
I have tried to create a stub by the "standard" C++ application template where I chose a project name that contained space characters in the wizard dialogue. The generated small build specification contains unusable parameters because there are some quotation marks missing in the build script template.

Would you like to check and improve the consistency of reusable project names in any ways?
Comment 1 Andrew Crouthamel 2018-11-11 04:30:13 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-21 04:38:06 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-10 01:52:04 UTC
Thank you for reporting this issue 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 "REPORTED" when replying. Thank you!
Comment 4 Markus Elfring 2023-01-10 08:45:08 UTC
(In reply to Justin Zobel from comment #3)
Will the chances grow to fix questionable implementation details?
https://invent.kde.org/kdevelop/kdevelop/-/blob/b9cb571ab09402c624f4cf21286710a00c521c9d/app_templates/cpp/CMake/cmake_plaincpp/CMakeLists.txt
Comment 5 Igor Kushnir 2023-01-10 09:35:21 UTC
(In reply to Markus Elfring from comment #4)
> Will the chances grow to fix questionable implementation details?
> https://invent.kde.org/kdevelop/kdevelop/-/blob/b9cb571ab09402c624f4cf21286710a00c521c9d/app_templates/cpp/CMake/cmake_plaincpp/CMakeLists.txt
If you know where the problem is and how to fix it, please create a merge request at https://invent.kde.org/kdevelop/kdevelop/-/merge_requests. Make the changes grow instead of waiting for someone else.
Comment 6 Markus Elfring 2023-01-10 09:40:16 UTC
(In reply to Igor Kushnir from comment #5)
I would appreciate another bit of clarification according to affected aspects for desirable progress also for this bug report.
Comment 7 Igor Kushnir 2023-01-10 09:47:51 UTC
(In reply to Markus Elfring from comment #6)
> I would appreciate another bit of clarification according to affected
> aspects for desirable progress also for this bug report.
Very cryptic :) What exactly would you appreciate?
Comment 8 Markus Elfring 2023-01-10 09:54:13 UTC
(In reply to Igor Kushnir from comment #7)
Will any contributors get into the mood to respond with more constructive information to my initial question for this bug report?
https://bugs.kde.org/show_bug.cgi?id=325262#c0
Comment 9 Igor Kushnir 2023-01-10 10:02:17 UTC
(In reply to Markus Elfring from comment #8)
> Will any contributors get into the mood to respond with more constructive
> information to my initial question for this bug report?
> https://bugs.kde.org/show_bug.cgi?id=325262#c0
> Would you like to check and improve the consistency of reusable project names in any ways?
All KDevelop contributors are volunteers that improve the IDE in their free time. Often to scratch their own itches. If no contributor is sufficiently bothered by a naming issue in project templates, then nothing gets done.

A few merge requests related to naming in templates have been merged in recent years: https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/96 and https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/206