You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get the following when trying to commit with magit since I updated to Fedora 30 (via reinstall) the other day:
1 git … commit --
hint: Waiting for your editor to close the file...
Waiting for Emacs...
*ERROR*: Wrong type argument: stringp, nil
error: There was a problem with the editor '/usr/bin/emacsclient --socket-name=/tmp/emacs1000/main'.
Please supply the message using either -m or -F option.
The one thing that I can think of might have caused this is that the reinstall meant new versions of all packages (incluing magit and with-editor).
My Config (I don't expect you to browse through that, just posting for completeness).
Can you try evaluating (setq debug-on-signal t) just before the comitting. That should cause a *Backtrace* buffer to pop up with more info on the error.
It didn't (no idea why) however when I looked in *Messages* I saw something else:
Error enabling Flyspell mode:
(stringp nil)
There's something weird going on with flyspell on my end (even just running flyspell-mode) fails here so really not a with-editor problem. Sorry for the noise!
Errors that occur when running git-commit-setup-hook are now demoted. Might make it harder for users to note that there is an issue but easier to narrow it down. And even if this results in some beloved feature being disable it makes it at least possible to commit without having to debug first.
I get the following when trying to commit with
magit
since I updated to Fedora 30 (via reinstall) the other day:The one thing that I can think of might have caused this is that the reinstall meant new versions of all packages (incluing magit and with-editor).
My Config (I don't expect you to browse through that, just posting for completeness).
M-x with-editor-debug
gives me:My
EDITOR
env var is:EDITOR=emacsclient -c -nw -s main
.The text was updated successfully, but these errors were encountered: