On 12/25/22 16:02, Jensen Bean wrote: > Thank you for filling out a Git bug report! > Please answer the following questions to help us understand your issue. > What did you do before the bug happened? (Steps to reproduce your issue) > download git > What did you expect to happen? (Expected behavior) > CTRL button to work > What happened instead? (Actual behavior) > CTRL button stops working > What's different between what you expected and what actually happened? > the CTRL button doesn't work when I have git installed > Anything else you want to add: > Deleting git and all its files has been the only thing that works so far > Please review the rest of the bug report below. > You can delete any lines you don't wish to share. > Confusing experience, wasn't sure what to actually do > > [System Info] > git version: > git version 2.38.1.windows.1 > cpu: x86_64 > built from commit: b85c8f604d375d4d773a36842964e8a7ec056aae > sizeof-long: 4 > sizeof-size_t: 8 > shell-path: /bin/sh > feature: fsmonitor--daemon > uname: Windows 10.0 22621 > compiler info: gnuc: 12.2 > libc info: no libc information available > $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe > > > [Enabled Hooks] > not run from a > git repository - no hooks to show > git-bugreport-2022-12-25-0152.txt[+] [unix] (01:52 25/12/2022) > Thanks for the bug report but you need to send it to Git mailing list, in order for developers there to see the report and act on it. Also, when replying, don't top-post; reply inline with appropriate context instead. If you top-post, I'm going to cut the whole context below. Thanks. -- An old man doll... just what I always wanted! - Clara
