You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When writing the command name help or h into the commandline it does not activate the help view like it does with the shortcut <?>
To Reproduce
Steps to reproduce the behavior:
Go to 'commandline ":"'
Write 'help' or 'h'
Press 'enter'
Nothing happens
Expected behavior
Help menu should appear like it does with the hotkey "<?>"
Versions (please complete the following information):
K9s: v0.27.4
K8s: v1.26.3
Additional context
When you type the command "help" or "h" in the function "helpCmd(evt *tcell.EventKey)" the first if statements renders as
a.CmdBuff().InCmdMode() = true
top != nil = true
top.InCmdMode() = false
Resulting as entering the first if statement and returning with "evt".
I don't know why is there a check for a.CmdBuff().InCmdMode() which checks the len(c.buff)>0 which prevents helpCmd from executing if help is typed into the commandline and not activated by hotkey. Probably for the hotkey to not trigger when typing?
The text was updated successfully, but these errors were encountered:
Describe the bug
When writing the command name help or h into the commandline it does not activate the help view like it does with the shortcut <?>
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Help menu should appear like it does with the hotkey "<?>"
Versions (please complete the following information):
Additional context
When you type the command "help" or "h" in the function "helpCmd(evt *tcell.EventKey)" the first if statements renders as
Resulting as entering the first if statement and returning with "evt".
I don't know why is there a check for a.CmdBuff().InCmdMode() which checks the len(c.buff)>0 which prevents helpCmd from executing if help is typed into the commandline and not activated by hotkey. Probably for the hotkey to not trigger when typing?
The text was updated successfully, but these errors were encountered: