Should work relative to wanted letter instead of alphabetic.

[daphen]

Wouldn't it be nice if I did something like "Shortcut+k" and the first occurrence of the letter was placed on the key I was searching for (I.E the letter k in this case) instead of on "a" every time?
The rest of the occurrences would then be placed from the letter in question instead of alphabetically.
If we use k as an example on a regular qwerty, it would then be:
First occurrence: "k",
Second occurrence: "l",
third occurrence: "j",
fourth occurrence: "m",
etc....

I think that would boost the speed at least for me, by about 100%.

[ice9js]

Interesting point. It would require you to define your keybindings in the plugin configuration in addition to your key bindings, since that is outside of the scope of the plugin. But since it can be implemented without changing any existing behaviour, I'm all in for it.

Unfortunately, I can't give you any estimates on when it will be done, as I have a lot of stuff going on at the moment.

[daphen]

Hm, I'm not 100% sure I understand what you mean by the "It would require you to define your keybindings in the plugin configuration in addition to your key bindings", but I'm happy you responded so quickly and that you're looking into it. I'm not in a rush at all, I just thought I would share my thoughts since I use this plugin kind of a lot. :)

[ice9js]

Since you can define your own shortcuts for AceJump commands outside of plugin configuration, it's impossible to access that information from the plugin.

Because of that, you would need to repeat these shortcuts in the AceJump config.

[daphen]

Do you mean that I would have to configure this manually, for every key?
Or am I dumb and just misunderstanding you? 😂

[ice9js]

Basically you'd have to configure what letter you want to start on for each command.

And what do you think should happen when you get to the last letter ? Should it stop there, or should it loop until it reaches the letter you started on ?

[daphen]

So, manual settings for each key. That's tedious. There's no way to scan for kayboardlayout and make a small algorithm to place the closest keys?
I mean, putting the first occurrence on the key you clicked might be easy, but the ascending occurrences to be placed on the keys closest to it might be really tricky.

[ice9js]

Oh wait, I misunderstood your example a little bit. But unfortunately, I have no idea to check which key combination triggered the command, and I have no way of checking your actual keyboard layout.

So the only way to make this work, would be through more extensive configuration.

[daphen]

You wouldn't need to know the key combination that triggered it, it would just be which key you're looking for. The one that gets highlighted, you must get that information at least I guess?

[ice9js]

Alright, now I get it... Ironically, that makes it more complicated than I thought. I don't have a clear way of how to do that now, but I'll give it some thought.

[daphen]

Haha, alright dude. Nice talking to you. Sorry if I gave you a headache. 😄