-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jordon-magit not working #1
Comments
Hmm, I haven't been able to figure out what could cause that, both commands are working for me. Were you able to sort this out? |
Sorry, I haven't had time to look at it completely. I'm guessing it's some setting in my init file that is messing it up. I will take a look as soon as possible. |
I tried to run the code with a fresh init file only loading magit and I get the same errors. The following code is the init file I use. As you can see I use el-get and fetch magit with that, but it shouldn't make a difference.
I fire up Emacs with If you have the time to give it a look that would be great. What emacs and magit, versions are you running? I will see what I can figure out. As I said, It looked like it was working once. Happy New-year btw! |
Are you calling What happens when you run |
The error arises when I run |
I've still been unable to reproduce this. I'm going to close this. |
I understand. Thank you for your time. |
Time to eat my words, I'm able to reproduce it now, I'll open this back up and work on it soon.
|
Ok, at least I'm not crazy 😊. Thanks again. |
Hi,
Thought I move the debugging here not to spam the emacs.stackexchange thread.
Hope you don't mind.
I am trying to run your jordon-magit but with the error that
If I run
I seem to get the correct info, name of file start line and number of lines of region.
if I run the cleanup script it cleans up the magit buffer as expected but when running the jordon-ispell
it errors.
(I swear it was working for 1second and I can't figure out how!)
If you have any idea or have time to help it's greatly appreciated.
The text was updated successfully, but these errors were encountered: