Awn

I agree with this. +1

This is probably expected behaviour. Dumping random data into the terminal isn't safe, write it to a file instead or pipe it into another program

@raginpirate > I think the UX on the disable option in settings is misleading. Usage of the term "all repositories" is not true when it is still fetching the current...

It's reaaaaly slow for me too. Takes a good four seconds to give a suggestion, making it more annoying than the command that fucked up in the first place.

``` ~/github/edgychat dev/crypto ✔ 0m ▶ cler zsh: command not found: cler ~/github/edgychat dev/crypto ✔ 0m ⍉ ▶ fuck DEBUG: Run with settings: {'alter_history': True, 'debug': True, 'env': {'GIT_TRACE': '1',...

Just an update on this: I've noticed that it's most slow after not using it for a while. So if I use it one day, and then use shell normally...

Hey 👋 thanks for reporting this Are you able to reproduce this issue outside of the container? What's the container image that's being used?

@firelizzard18 for Delve specifically it looks like the issue was [resolved](https://github.com/go-delve/delve/issues/3490) @powersj looks like an interesting approach, but it's probably not portable between platforms.

This is most likely because debug mode prevents Mlock. Unfortunately memguard doesn't currently support disabling Mlock

Hi, thanks for the PR. I'm sorry I haven't had time to review it yet