Index out of range error causes Panic with example Vim bindings about superfile HOT 10 CLOSED

ok going back to the default config certain keys also cause it (pretty much anything except up/down and 'q' actually)

As for this issue I think it's most likely due to incomplete support for windows. Can you send error?

Thank you so much!

adding '' to every binding does fix it
I think it was the same issue for the default bindings as some do seem to have a single entry (it was the same stack trace as in the original comment)

from superfile.

this doesn't happen if the hotkeys file is the default bindings

from superfile.

if I add a second keybinding 'down' and 'up' to the vim list_down and list_up keybindings it doesn't happen (but still happens for any binding that only has 1 key bound it seems)

from superfile.

ok going back to the default config certain keys also cause it (pretty much anything except up/down and 'q' actually)

from superfile.

Whoops, sorry that's an update to the current latest version I forgot that this affects the previous version I'll change it to the old one first and then make the change!

If you want to solve it now you just need to change each array to ['key', ''].

from superfile.

ok going back to the default config certain keys also cause it (pretty much anything except up/down and 'q' actually)

As for this issue I think it's most likely due to incomplete support for windows.
Can you send error?

Thank you so much!

from superfile.

ok going back to the default config certain keys also cause it (pretty much anything except up/down and 'q' actually)

As for this issue I think it's most likely due to incomplete support for windows. Can you send error?

Thank you so much!

actually I'm not sure what I did, I must have mixed the configs wrong or something because now I'm not seeing the issue with the default one. (and it does not have any with a single binding)
sorry for false report on that one

from superfile.

actually I'm not sure what I did, I must have mixed the configs wrong or something because now I'm not seeing the issue with the default one. (and it does not have any with a single binding)
sorry for false report on that one

Did you copy the default settings from the website?
If so, then I think it’s the same problem!

I appreciate you reporting this docs issue! :)

from superfile.

I guess that was probably it.
this seems like a good/solid file manager but in my opinion probably shouldn't crash/panic if there is a misconfiguration.. is this just docs issue?

from superfile.

I guess that was probably it. this seems like a good/solid file manager but in my opinion probably shouldn't crash/panic if there is a misconfiguration.. is this just docs issue?

I think this could also be considered a bug and I should add some hint to indicate to the user that there is an error in the setting file instead of having it panic...

from superfile.