Sometimes the prompt is lost and becomes ==emacs==ret=0==.

[apteryks]

Hi,

I sadly don't have a reproducer at hand, but this is something I see somewhat regularly in my Emacs 30.1 (and before that, in Emacs 29 as well); sometimes just pressing RET (enter) without any command triggers it in M-x shell, like just occurred:

maxim@terra ~/src/opendht$ 
==emacs==ret=0==.
==emacs==ret=0==.
==emacs==ret=0==.

Looks like a single RET caused the problem. I wasn't in any guix shell or otherwise special environment.

[szermatt]

What version of bash are you running? On which OS ? Something may have changed in recent Bash versions that broke emacs-bash-completion.

[szermatt]

I can reproduce it with Bash 5.2.37 on macos; if a command fails, the prompt is overwritten. This affects older version of emacs-bash-completion, so it's very likely an incompatibility with newer versions of Bash.

[apteryks]

I'm using GNU bash, version 5.1.16(1)-release (x86_64-unknown-linux-gnu), on the Guix System OS.

[szermatt]

I pushed a change which I think will solve the issue you're having.
Please let me know if that doesn't work for you.

That said, I think that you're having this issue when you just type RET because something calls completion-at-point very generously, like completion-preview-mode or corfu-auto would.

I'd suggest checking your configuration and turning off any such auto-completion mode for shell buffers, because shell completion can be very slow and expensive, so this is something that's best triggered manually.

[apteryks]

I think perhaps it was company-mode? That seems to be the only auto-completion used in my case. I'll try your fix, thanks for working on it so promptly!

[apteryks]

Works well so far!