-
Notifications
You must be signed in to change notification settings - Fork 61
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
startup error on ubuntu 14.04 - works find on OSX #50
Comments
Hmm, looks like it may be an issue with package.el rather than ag.el. Is that the full traceback? It's not clear to me what's calling |
Here is the complete output -
|
The traceback mentions functions Also, it's suspicious that ag is simply the first package alphabetically. If you remove ag and try again, do you still get the error? |
I am closing this issue. I started removing packages from my config and I still get the arrayp without loading up 'ag package. I must be missing a dependency somewhere as this is a clean env I am setting up. |
I am running ubuntu 14.04 with GNU Emacs 24.3.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.10.6). I have the same config on OSX and it works fine. I am getting the following error on startup.
Wrong type argument: arrayp, ([cl-struct-package-desc ag (20140322 948) A front-end for ag ('the silver searcher'), the C ack replacement. nil nil nil /home/dhill/.emacs.d/elpa/ag-20140322.948 nil nil])
When I enable debub-init I get
Debugger entered--Lisp error: (wrong-type-argument arrayp ([cl-struct-package-desc ag (20140322 948) "A front-end for ag ('the silver searcher'), the C ack replacement." nil nil nil "/home/dhill/.emacs.d/elpa/ag-20140322.948" nil nil]))
aref(([cl-struct-package-desc ag (20140322 948) "A front-end for ag ('the silver searcher'), the C ack replacement." nil nil nil "/home/dhill/.emacs.d/elpa/ag-20140322.948" nil nil]) 0)
(memq (aref package-info 0) cl-struct-package-desc-tags)
Any thoughts on how to fix this. I am new to emacs so if I need to run more tests please let me know.
The text was updated successfully, but these errors were encountered: