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
When I set $env:MCFLY_KEY_SCHEME="vim" in my Powershell profile (aka "config file"), mcfly fails to start on the first few tries, and then it duplicates every key press (i.e. typing "a" results in "aa", "j" results in "jj")
PowerShell.2024-08-13.09-23-57.mp4
This issue persists even if I set $Env:MCFLY_KEY_SCHEME = 'vim' (capital E, single quotes around 'vim', spacing between assignment) as shown in the official Powershell docs
The text was updated successfully, but these errors were encountered:
@cantino so I don't use Windows predominantly (only for work), but it did just occur to me that Powershell has a native vi mode, and I do have that enabled. I'll check later to see if this problem persists when I turn it off
For the record, the default emacs keybindings work well on my system (i.e. with Powershell using vi mode)
Okay, just tried setting Powershell's vi mode off, and it's still happening
I can also confirm that the double keypresses make the vim navigation unusable, since the first escape puts it into command mode, and then the second one (immediately afterwards) quits mcfly
When I set
$env:MCFLY_KEY_SCHEME="vim"
in my Powershell profile (aka "config file"),mcfly
fails to start on the first few tries, and then it duplicates every key press (i.e. typing "a" results in "aa", "j" results in "jj")PowerShell.2024-08-13.09-23-57.mp4
This issue persists even if I set
$Env:MCFLY_KEY_SCHEME = 'vim'
(capital E, single quotes around 'vim', spacing between assignment) as shown in the official Powershell docsThe text was updated successfully, but these errors were encountered: