eshell-did-you-mean doesn’t seem to work. Any invalid command just returns Wrong type argument: sequencep, 771
I only noticed something odd was happening because I was getting an error when I reloaded my config with space h r r, but only if I had previously opened eshell with space o e.
Running emacs with --debug-init traced the error to the eshell-did-you-mean--edit-distance being passed 771 as s2
If I comment the eshell-did-you-mean section out of the eshell config.el, I no longer get an error on reloading my config.
What did you expect to happen?
For instance I expected entering catt into eshell would return
did you mean cat
Did you ever manage to fix this? I’m having the same issue, same error message when I enter an invalid command in eshell (doesn’t matter how I open it though, with M-x eshell or SPC-o-e or M-x project-eshell it’s all the same).
I hadn’t seen any config error messages, but I tried SPC-h-r-r after opening eshell with SPC-o-e like you said, and lo and behold:
Error in a Doom module: /home/charriso/.config/emacs/modules/term/eshell/config.el, (wrong-type-argument sequencep 771)
I notice you’re also on Mint. For additional context, this wasn’t happening to me at all until I upgraded from Emacs 27 to 28.1 (native comp). It’s not super critical so I’m not gonna spend any more time chasing it down but I thought I’d leave this info here as another data point.