Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

magit interactive rebase stops with no error message #599

Closed
quodlibetor opened this Issue · 4 comments

3 participants

Brandon W Maister Yann Hodique Jonas Bernoulli
Brandon W Maister

When I'm in *magit-log* and press E nothing visible happens. When I press $ I see:

$ git --no-pager rebase -i d2c2d86^

# If you remove a line here THAT COMMIT WILL BE LOST.[24;63H2,1[24;77HTop[2;1H

If I then try to do anything else (e.g. stage a file) I get the message magit-run*: Git is already running, and the *magit-process* buffer doesn't change at all.

This has been happing for a long time (at least a month, probably 2).

Emacs versions 24.2 and 24.3
git version 1.8.0.1 (but I've upgraded a few times, and it's happened on the last few versions of git too)

I've been keeping up with magit via marmalade, so I think that I've been on master for the last few months.

Yann Hodique
Owner

That's strange, it looks like the git rebase command uses the current buffer as editor. Can you check your Messages buffer to see if there's any complaint regarding emacs-client ?
That would look like: Cannot find emacsclient, using default git editor, please check you PATH

If that's the case, well, please check your PATH :)

Brandon W Maister

@sigma Wow, yeah, that's exactly what's going on. Thank you!

Yann Hodique
Owner

can I assume that with a correct PATH you get the desired behavior? if not, feel free to reopen

Yann Hodique sigma closed this
Brandon W Maister

Sorry, I should have mentioned that what I actually needed to change was exec-path to include where I had compiled emacs. (You'd think that configure --prefix=$HOME/.local/bin would add that dir to exec-path by default.)

But yeah with that change it works perfectly, thank you.

Jonas Bernoulli tarsius added this to the 2.1.0 milestone
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.