Replies: 2 comments
-
thanks, I never knew F1 opened command palette, that's way easier. you don't want F1 to be remapped to I just tested the functionality of Personally, if it's to search an ahk command, I double click the command (for example WinGetTitle) to select it and I use ctrl+right click $^Rbutton::
gotClip:=getClip()
runCommand := """C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"" ""https://www.autohotkey.com/docs/commands/" gotClip ".htm"""
Run, %runCommand%
return
getClip()
{
clipboard=
Send, ^c
Send, ^c
sleep, 50
return clipboard
} |
Beta Was this translation helpful? Give feedback.
-
Yeah, that seems like a major oversight. I will do my best not to use keybindings that are also defaults in VS Code. |
Beta Was this translation helpful? Give feedback.
-
Please, would you consider not including the keyboard shortcut for accessing AHK's documentation introduced here?
I could be wrong but I believe F1 has always been a VSC default keybinding along with Ctrl+Shift+P for accessing the command palette. Personally, I simply access the documentation from a shortcut placed in Window's quick-launch toolbar and trying to un-train muscle-memory for using F1 to access the command palette has proved to be a little irritating.
Beta Was this translation helpful? Give feedback.
All reactions