Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GeanyLua Plugin] Keybindings are based on line order of hotkeys.cfg file #1388

Open
advice2020 opened this issue Nov 22, 2024 · 0 comments
Open

Comments

@advice2020
Copy link

advice2020 commented Nov 22, 2024

Not sure if this is how all Geany plugins handle keybindings or just this specific plugin, but I noticed a possible issue.
Probably the only way to program this so it might not really be something that can be fixed, but can make things a little confusing.

-This plugins requires user to create "hotkeys.cfg" file.
-In this file user adds <path-to-lua-script>/<script-name>.lua to each of their Lua scripts, one per line.
-The order of these path/name lines in this file determine the order that they show up in "Preferences - Keybindings - Lua Script"

-Then assign keybindings to each of these items linked to your Lua scripts.
-However if you end up changing/rearranging the line order in the "hotkeys.cfg" file after doing so this is where the issue occurs.
-The keybindings seem to be linked to the line numbers only, not the scripts, so when this occurs now different scripts will be assigned to those previous keybindings, so this could be dangerous depending on what those new scripts do.

Again, not sure if anything can really be done to fix this, probably not.
If not, I have not checked yet but if is does not already exist, might want to mention this somewhere so users can be aware of this.

Thank You

EDIT:
I apologize the "mentioned this issue" link below was just meant to let some users know of this possible issue, but the two posts are not related. I tried not to link this actual post number, but it did, and now I cannot seem to remove the link even though I editied it in the other post. So just ignore it I guess, unless there is a way to remove it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant