<p></p>
<blockquote>
<p>That's actually quite a useful feedback because as a non-vim user</p>
</blockquote>
<p>Not really, what would be useful would be for a vimist to list the missing/erroneous functionality to make a minimal usable vim like UI (hint hint <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/howdev/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/howdev">@howdev</a> <g-emoji class="g-emoji" alias="grin" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f601.png">😁</g-emoji>).  Then you can determine the scope of the problem instead of chipping away at an edge case at a time and it remaining unusable.  We all know you love a challenge, (mentioning no ctags by name) so knowing the size of the job would be helpful.</p>
<p>Knowing you have to re-implement every piece of editor.c [minor exaggeration for effect] due to edge case semantic differences in how things work is important.   Although its (literally) many decades since I used vi/vim in anger, from my memories I have my doubts that it will implement as a simple UI wrapper around Scintilla and existing Geany functionality, so I would be interested to see what is required.  And of course Vim has changed significantly in that period, hence needing to tease out details as above to reach the <a href="https://github.com/geany/geany-plugins/issues/1060#issuecomment-773775126" data-hovercard-type="issue" data-hovercard-url="/geany/geany-plugins/issues/1060/hovercard">conclusion</a> of what semantics need to be different to those of existing Geany functionality.</p>
<blockquote>
<p>And if something is broken, everyone should be allowed to say so.</p>
</blockquote>
<p>So long as they say <em>what</em> is broken, and I continued to work with the OP to tease out the actual difference between vim and vim plugin in detail, and not simply in negative terms.  I don't see it as discouraging reports to steer them away from simple negative statements to providing useful information.</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-plugins/issues/1060#issuecomment-899152363">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAIOWJ3VVTWU7F44XJRMDT3T5BSJDANCNFSM4XACB2DA">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&utm_campaign=notification-email">Android</a>.<img src="https://github.com/notifications/beacon/AAIOWJYZYSTKOKHABEYMHPTT5BSJDA5CNFSM4XACB2DKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGWL7T2Y.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-plugins/issues/1060#issuecomment-899152363",
"url": "https://github.com/geany/geany-plugins/issues/1060#issuecomment-899152363",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>