Closed
Description
EXPLAINSHELL_ENDPOINT
is there to configure the source of the explainshell service, whether it would point to explainshell.com or a local Docker container. I would envision people to configure this environment variable somewhere globally, do it once and forget.
However, there could be times when the explainshell service is not running: Docker container image is stopped, or you have no internet access at the moment.
Currently, when EXPLAINSHELL_ENDPOINT
is set, but the endpoint is not available, the editor is being spammed with an error:
I would like to propose to silently ignore this specific case, when the endpoint is not available, and just continue to try the other existing methods of getting the hover information.
What do you think?