when possible (python, golang and many others) I just go and read the source..

I wonder why people come to conclusion like that to that specific problem.

surely the user may knows that there is probably zillions (by that i mean a lot) of users using gmail via IMAP (at least the enterprise accounts) don't you think it's maybe something else you are doing that flags your account

The main point is that a paying customer shouldn't have to guess at why they were flagged.

This Omarchy remind me of Linux-Mandrake from back in the day, a collection of badly written shell script but that "works"

i wish python had something liek that to be honest

one can dream but i wouldn't keep high hopes. I feel functional patterns are left as second class citizens in python.

you have a .deb there https://www.microsoft.com/en-us/edge/download?form=MM145U (i don't use it, just saying)

If it were a longstanding bug versus one just created for this exercise a git diff may not help much. Imagine you've found some edge case in your code that just hadn't been properly exercised before. It could have been there for years, now how do you isolate the erroring section? This technique (or the one I mentioned in my other comment which is very similar but uses more data) can help isolate the problem section.

git diffs can definitely help with newer bugs or if you can show that it's a regression (didn't error before commit 1234abcd but did after).

"Wait, what did I change that impacted that test?"

An intersection between code coverage and a git diff once answered that handily for me.

nice idea but i get that error when i try to use the docker image (on a nixos env)

NameError: name 'SRE_FLAG_TEMPLATE' is not defined. Did you mean: 'SRE_FLAG_VERBOSE'?

(using the mentioned docker command on README $ docker run --rm -v `pwd`/nginx.conf:/etc/nginx/conf/nginx.conf getpagespeed/gixy /etc/nginx/conf/nginx.conf)

:! itself has not been stripped from neovim, it's the "interactive" :! that has been stripped (as the OP said)

i.e if you do :!bash in vim you enter bash in neovim you won't

Thanks for the clarification. That makes sense and seems like a reasonable change to me.

I wouldn't say that `:!bash` is the most illustrative example of its impact. It bites you when you run any command that spits out a prompt, most commonly a [Yn] prompt. You can't use `:!` for these in nvim.

it's interesting to see how emacs have seen a renaissance lately with AI there is so many good modes to interact with LLM not the way the other editors does it but more of a Emacs way. for example gptel https://github.com/karthink/gptel