Whilst configuring bindings in $HOME/.config/micro/bindings.json, I encountered the following error:
Error in bindings: action InsertSpace does not exist
Confusion
This was strange to me, as the documentation for key bindings clearly states the existence of an InsertSpace value as a bindable key. It seems as though this list is currently not only incomplete, but also has some wrong values that have stuck there for years, notably the presence of InsertSpace.
Related issues and pull request
This has led me to stumble upon various issues and a pull request, none of which having been addressed for a few years at this point.
Notably, these:
This can be marked as duplicate, but I feel as though bringing everything in a single place and putting some more recent attention to the issue may be for the best at this point in time. The relevant open issues are still open to be addresses individually, if needs be.
Possible fixes
Removing InsertSpace from the documentation
Whilst this would be the least ideal solution, it would at least clear up the confusion. This is a simple one-liner change. Additionally, if needs be, any further tweak/fix to the documentation would be ideal if this issue already has a solution that is not documented clearly.
Re-adding the InsertSpace keybind
This would solve the issue at hand, and the documentation would not have to be changed.
Ability to bind any standard key
This is, after the first solution, both the leastandbest way to tackle the issue; It could take a lot of effort that could be spent elsewhere, and it may break things, but it would also fix the issue and give the users a much greater amount of customizability.
Issue
Whilst configuring bindings in
$HOME/.config/micro/bindings.json, I encountered the following error:Confusion
This was strange to me, as the documentation for key bindings clearly states the existence of an
InsertSpacevalue as a bindable key. It seems as though this list is currently not only incomplete, but also has some wrong values that have stuck there for years, notably the presence ofInsertSpace.Related issues and pull request
This has led me to stumble upon various issues and a pull request, none of which having been addressed for a few years at this point. Notably, these:
Why make this issue?
This can be marked as duplicate, but I feel as though bringing everything in a single place and putting some more recent attention to the issue may be for the best at this point in time. The relevant open issues are still open to be addresses individually, if needs be.
Possible fixes
Removing
InsertSpacefrom the documentationWhilst this would be the least ideal solution, it would at least clear up the confusion. This is a simple one-liner change. Additionally, if needs be, any further tweak/fix to the documentation would be ideal if this issue already has a solution that is not documented clearly.
Re-adding the
InsertSpacekeybindThis would solve the issue at hand, and the documentation would not have to be changed.
Ability to bind any standard key
This is, after the first solution, both the least and best way to tackle the issue; It could take a lot of effort that could be spent elsewhere, and it may break things, but it would also fix the issue and give the users a much greater amount of customizability.