<p></p>
<p>I'm doing something like <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/elextr/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/elextr">@elextr</a> suggestion (ugly I know):</p>
<p><code>rm -rf ~/.cache/geany_config; cp -L -r ~/.config/geany/ ~/.cache/geany_config; geany -c ~/.cache/geany_config; rm -rf ~/.cache/geany_config</code></p>
<p>Maybe there are other configs statements to 'extract', like geometry, for the scope of put geany.conf in a VSC. In addiction, the geany.conf file is generated at first start with a lot of default configs. I did a try removing them and keep just what I did change, but the editor will put them again.</p>
<p>I think that can be a useful feature to have a way to add just a subset of instructions/configs in a file to enhance/customize the behavior of geany, like themes or external commands. Maybe a better way to do so can be the use of something like a geany.d folder with custom files to be read when exist, and that can overwrite the configs in geany.conf... What do you think?</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/1763#issuecomment-708077234">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAIOWJ4ZQVRBQA62I7EHFPDSKTUPXANCNFSM4EPZHXFA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AAIOWJYXXXDE6LB447E3KTLSKTUPXA5CNFSM4EPZHXFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFI2GNMQ.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/1763#issuecomment-708077234",
"url": "https://github.com/geany/geany/issues/1763#issuecomment-708077234",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>