Would LOVE the ability to use ARROWS in the cheatsheet

[pixelrogue1]

Just discovered LeaderKey and see myself digging deep - this looks like might be amazing.

The first thing I went to set up were shortcuts to various folders (most deeper folders around a NAS.)
Now, when you have about 20 of them, assigning and expecting to memorize each key for each location.
Enter stage right, the Cheatsheet. Cheatsheet is so handy...now, still too much to expect hitting second key....
The Cheatsheet is great and BEGS to use the keyboard arrows...activating LK and then arrows is such an intuitive flow.

Can LK please support arrow navigation (along w/return) in the Cheatsheet?
(ironically, the arrows do generate movement of the cheatsheet, nudging the windows slightly.)

[mikker]

I see your idea but feel it kinda goes into some other territory. Almost like file system traversal. I can see that it could be useful but the purpose of the cheatsheet isn't navigation, it's to help you remember and learn fixed shortcut keys.

Might consider this some day but not sure it's a direction I see for LK.

Thanks!

[pixelrogue1]

Surprised by the fast and personable reply - thank you. Clearly building muscle memory requires repetition. Building and binding shortcuts, scripts, complex combos all benefit from muscle memory.LK is built to be the fastest access point to just about everything. File system locations, for a large set of users, might be of the single most accessed task on any given day…yes, file traversal. There are more valuable and efficient uses for muscle memory than managing and memorizing shortcuts for each location when you have more than about 5; in addition maybe 3-5 out of 20 might be used more frequently and access to the remaining 15 spots are off equal priority.One does not benefit from memorizing shortcuts to each folder and it adds unnecessary cognitive friction. Tap an LK shortcut to show a defined list of folders, arrow down would be the simplest work flow.Now, there was a part-b to the idea that was intentionally omitted because part-b might have risk of introducing a concept moving into another territory. Part-b would be small file management actions, so ability to move a file through LK. I see this as being a huge time saver and consistent with LK (compress file and move to x location) and can see some thinking the idea lives in more of a gray area, not germane to LK purpose.  On Oct 22, 2025, at 7:08 AM, Mikkel Malmberg ***@***.***> wrote: I see your idea but feel it kinda goes into some other territory. Almost like file system traversal. I can see that it could be useful but the purpose of the cheatsheet isn't navigation, it's to help you remember and learn fixed shortcut keys. Might consider this some day but not sure it's a direction I see for LK. Thanks! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[mikker]

It's not a dumb idea. Not doing it now but I'll this post sit for later

[pixelrogue1]

Actually just thought of a similar example from one of the product videos…showing how LK can be used to turn on/off a light (which was cool to include in the video btw.)We have 21 lights (and apx 35 other iot devices.)  I find myself working from either the home office of living room , even division at times. Not good use of muscle memory to memorize and correlate three different lights as commands would vary by location. Instead, one command to toggle light switch and arrow key to pick location.Sent from my digital implant....On Oct 22, 2025, at 7:35 AM, Peter Robberts ***@***.***> wrote:Surprised by the fast and personable reply - thank you. Clearly building muscle memory requires repetition. Building and binding shortcuts, scripts, complex combos all benefit from muscle memory.LK is built to be the fastest access point to just about everything. File system locations, for a large set of users, might be of the single most accessed task on any given day…yes, file traversal. There are more valuable and efficient uses for muscle memory than managing and memorizing shortcuts for each location when you have more than about 5; in addition maybe 3-5 out of 20 might be used more frequently and access to the remaining 15 spots are off equal priority.One does not benefit from memorizing shortcuts to each folder and it adds unnecessary cognitive friction. Tap an LK shortcut to show a defined list of folders, arrow down would be the simplest work flow.Now, there was a part-b to the idea that was intentionally omitted because part-b might have risk of introducing a concept moving into another territory. Part-b would be small file management actions, so ability to move a file through LK. I see this as being a huge time saver and consistent with LK (compress file and move to x location) and can see some thinking the idea lives in more of a gray area, not germane to LK purpose.  On Oct 22, 2025, at 7:08 AM, Mikkel Malmberg ***@***.***> wrote: I see your idea but feel it kinda goes into some other territory. Almost like file system traversal. I can see that it could be useful but the purpose of the cheatsheet isn't navigation, it's to help you remember and learn fixed shortcut keys. Might consider this some day but not sure it's a direction I see for LK. Thanks! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>