<p></p>
<p>27 December 2020<br>
8 PM</p>
<p>The good news:</p>
<p>I've figured this out.  See: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="775150116" data-permission-text="Title is private" data-url="https://github.com/geany/geany/issues/2708" data-hovercard-type="issue" data-hovercard-url="/geany/geany/issues/2708/hovercard" href="https://github.com/geany/geany/issues/2708">#2708</a></p>
<p>The bad news:</p>
<p>The bug is completely deterministic and much worse than I thought.</p>
<p>I won't trouble you with the details of false correlations, mis-directions, confusion and frustration that has beset me the past few days.</p>
<p>Suffice it to say that if we hadn't butted heads over our very different experiences with geany, I never would have looked at the things that I needed to look at to resolve the ambiguities.</p>
<p>Long story short: we are both right.</p>
<p>You are correct that geany is designed for single execution.</p>
<p>I am correct that all I have ever experienced is a wonderful development environment for multiple simultaneous processes.</p>
<p>I am now closing this issue, which is only useful in the sense that it led to clear understanding as expressed in: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="775150116" data-permission-text="Title is private" data-url="https://github.com/geany/geany/issues/2708" data-hovercard-type="issue" data-hovercard-url="/geany/geany/issues/2708/hovercard" href="https://github.com/geany/geany/issues/2708">#2708</a></p>
<p>Resolving <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="775150116" data-permission-text="Title is private" data-url="https://github.com/geany/geany/issues/2708" data-hovercard-type="issue" data-hovercard-url="/geany/geany/issues/2708/hovercard" href="https://github.com/geany/geany/issues/2708">#2708</a> is up to you and the geany developers.  I can only hope you take heed of my concluding remarks.  As of now, I wash my hands of this and return to my other tasks, since I now have a deterministic understanding of how to control the anomalous behavior of geany that actually is not anomalous, but only very complicated.</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/2703#issuecomment-751549384">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAIOWJZ437MBIUI6RAF6QJDSW7SPTANCNFSM4VHMZG5Q">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AAIOWJ3Z2VISOHZFQNYYBTDSW7SPTA5CNFSM4VHMZG52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFTF3XSA.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/2703#issuecomment-751549384",
"url": "https://github.com/geany/geany/issues/2703#issuecomment-751549384",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>