<p></p>
<blockquote>
<blockquote>
<p dir="auto">Remove all the project code.</p>
</blockquote>
</blockquote>
<p dir="auto">Ok, "remove all the <strong>existing</strong> project code", obviously there is then new code based on my suggestion to be added.</p>
<blockquote>
<p dir="auto">This will break multiple plugins.</p>
</blockquote>
<p dir="auto">Why? Plugins should not be writing to these files directly, they should be writing to the <code>g_key_file</code> structure obtained from Geany, as <code>project-organiser</code> does.  It doesn't matter which file that structure maps to if it has the settings in it.</p>
<blockquote>
<p dir="auto">This breaks existing API.</p>
</blockquote>
<p dir="auto">Why?  We can leave project related functions, they just have to act on different structures inside Geany.  Then they can be deprecated for a few years, then they can be removed at a point that the ABI is broken anyway.</p>
<blockquote>
<p dir="auto">This breaks how users interact with projects.</p>
</blockquote>
<p dir="auto">Why?  I havn't even mentioned what the GUI should look like, and to be clear I would want it to be at least the current capability (but with a more intuitive <code>New Project</code> dialog).</p>
<blockquote>
<p dir="auto">This is the removal of an existing capability.</p>
</blockquote>
<p dir="auto">No, it is the extension of an existing capability to be much <strong>more</strong> capable, projects would be able to set <em>any</em> setting.</p>
<blockquote>
<p dir="auto">Users aren't given any choice in the matter.</p>
</blockquote>
<p dir="auto">Because there is no choice to make, unless for some reason a user wants to remain straight jacketed by the existing projects capability.  As I said above, it is not removing any capability so it doesn't need a choice by the user.</p>
<blockquote>
<p dir="auto">Apparently no longer an issue since the session_split branch has been merged without addressing it.</p>
</blockquote>
<p dir="auto">Guess <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/kugel-/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/kugel-">@kugel-</a> was persuaded enough not to worry.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/3015#issuecomment-976117388">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAIOWJ4DIGXTAXPUODCWLETUNL7N7ANCNFSM5ISB55XQ">unsubscribe</a>.<br />Triage notifications on the go with GitHub Mobile for <a href="https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675">iOS</a> or <a href="https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub">Android</a>.
<img src="https://github.com/notifications/beacon/AAIOWJ3KE6B5OVOQRAL2KL3UNL7N7A5CNFSM5ISB55X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHIXF5DA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/issues/3015#issuecomment-976117388",
"url": "https://github.com/geany/geany/issues/3015#issuecomment-976117388",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>