-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
evil-indent-textobjects fork is causing an error when installing #2688
Comments
It is still throwing the same issue for me as well. I have tried it on two windows 10 machines same version as above. Also it appears that I can't run package-buffer-info from M-x menu as it doesn't exist? I'm pretty new to emacs so I might be missing something. Could it possibly be related to the new use-package quelpa feature? |
You may have to |
gotchya. I'll see what I can do. |
Ah sorry, |
@mahinshaw When this happens, can you grab the file in the backtrace (c:/Users/Mark/.emacs.d/.cache/quelpa/packages/evil-indent-textobject-20140918.707.el) and post it somewhere so I can see? |
Interestingly enough, the error does not seem to show up on my win 7 work machine. @mahinshaw what version of windows are you running? |
@Devagamster - I am on Windows 7 - what emacs build are you using? |
http://emacsbinw64.sourceforge.net/ for both machines having the issue and my one machine that is not displaying the issue. They all have the same .spacemacs.d folder as well. |
That is what I am using as well. I tried an old build of 24.3 from gnu for windows, and I had the same issue. |
I can't reproduce this issue, not even with @mahinshaw's file. It must be OS/build related. I'll ask the quelpa maintainer to chip in. |
This is probably caused by Git for Windows defaulting to auto convert line endings to CR/LF (see quelpa/quelpa#72 (comment)) on checkout. Try disabling autocrlf:
See https://github.com/quelpa/quelpa#windows-instructions for Windows specific quelpa instructions (if the git change still didn't help, try if it works with any of the methods specified there) |
@steckerhalter Changing autocrlf to false did not solve the problem. |
@louy2 did you also wipe out the quelpa cache ? (~/.emacs.d/.cache/quelpa) |
I was able to reproduce this issue on my Windows computer. Setting According to @louy2, the |
I take that back, I was able to reproduce this with the |
@TheBB you can disable line-ending conversion in most people won't have this set so disabling autocrlf will be still required for other repos |
Thanks @steckerhalter, so after some mucking about, here are my findings.
|
As long as |
I don't know, I couldn't run with |
I'm getting a I can consistently get |
@syl20bnr Git for windows 2.5.0 has just been released Aug 18. |
@louy2 I haven't tested on Windows yet but with the change in quelpa it should also work now without setting autocrlf to false |
Works for me. Just as a side note - |
@mahinshaw it causes the same error as before with |
@steckerhalter I see it too, but I don't think it originates from the same location. Before, I got a backtrace on That's all I've found out for now. |
@steckerhalter Yes. I just tested it again myself, and the issue is still there when |
Ok, can you post the error if possible? |
@steckerhalter I don't get a dump from the debugger, but the error from spacemacs is:
I started from a fresh clone of spacemacs to make sure there were not any cache issues regarding spacemacs. I am also back to using |
Thanks. I will see if I can reproduce on Windows |
I know now why I used (defun package-install-file (file)
"Install a package from a file.
The file can either be a tar file or an Emacs Lisp file."
(interactive "fPackage file name: ")
(with-temp-buffer
(insert-file-contents-literally file)
(when (string-match "\\.tar\\'" file) (tar-mode))
(package-install-from-buffer))) So now it is failing in Emacs core because |
it's here in the emacs source code: http://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/emacs-lisp/package.el#n1961 |
Yeah I thought it would be something like that. There's probably not much we can do about it, then. Thanks for your help @steckerhalter! |
Can we advice install-from-buffer and do the conversion ? |
Advicing is quite dangerous as it may break other things (a good example is what happened with emacs-async that was advicing I wrote some code using |
I see, I will disable async compilation as we don't need it in Spacemacs (the update process of Spacemacs already forces a deletion of the packages to update and a restart to complete the installation, especially to fix the issue that async compilation tries to resolve). Nice solution, replacing the bound function locally is great. I cannot test for now unfortunately :-( |
This is with hack like this that elisp shines as a configuration language, having so much code that don't clash without namespace support is just epic :-) |
I could test in the meantime. Seems to work. The problem with async compilation was fixed btw by the maintainer a few days ago so that shouldn't be a an issue anymoe, but it was a good reminder to me never to advice any Emacs internals in public packages because it's impossible to know all the side-effects the changes could possibly have. |
Lisp is awesome... too bad it's not more popular and the world is stuck in the non-REPL world |
I went through a new installation of Git for Windows today, and noticed that to change the checkout behavior, it is enough to change |
@louy2 Yes, that's better probably, although one should see when committing that there's a huge diff and if there is a PR with that it will probably be rejected. The change I made in quelpa now (not merged yet) should make this problem go away so we can all forget about it. Then it will work no matter what someone chooses to have for autocrlf. |
I just tested quelpa/quelpa#86 and it works beautifully here. |
Thanks, merged as well |
@steckerhalter - I tested this again this morning. Works like a champ! |
Refers to #2656. When updating spacemacs, evil-indent-textobject throws an error when installing
using version -
GNU Emacs 24.5.1 (x86_64-w64-mingw32) of 2015-04-12 on KAEL
The text was updated successfully, but these errors were encountered: