I recently went Win7->Win10 on my work PC and org-agenda is now kicking an error.
GNU Emacs 26.1 (build 1, x86_64-w64-mingw32) of 2018-05-30
org 9.2.1
I've reduced my org-mode related .emacs down to the following and the issue is persisting.
(custom-set-variables
'(org-agenda-files (quote ("~/org/inWork.org")))
)
When I run org-agenda 'a', I get an empty agenda, dates only, nothing is captured from inWork.org. The minibuffer displays Wrong number of arguments: (0 . 0), 2
Running the same in debug mode gives a backtrace of
Debugger entered--Lisp error: (wrong-number-of-arguments (0 . 0) 2)
org-get-tags(nil nil)
org-agenda-get-deadlines()
org-agenda-get-day-entries("~/org/inWork.org" (2 7 2019) :deadline :scheduled :timestamp :sexp)
apply(org-agenda-get-day-entries "~/org/inWork.org" (2 7 2019) (:deadline :scheduled :timestamp :sexp))
org-agenda-list(nil)
funcall-interactively(org-agenda-list nil)
call-interactively(org-agenda-list)
org-agenda(nil)
funcall-interactively(org-agenda nil)
call-interactively(org-agenda nil nil)
command-execute(org-agenda)
org-agenda 't' fails similarly. I tried stripping down the org files and .emacs as much as possible, but I haven't been able to isolate the issue.
Any help appreciated.
I got the same error when I upgraded org. When I downgraded I could start the agenda again.
Difference between versions (Non-working/working):
Org mode version 9.2.1 (9.2.1-33-g029cf6-elpa # /home/sdaa/.emacs.d/elpa/org-20190225/)
Org mode version 9.2.1 (9.2.1-23-g126a37-elpa # /home/sdaa/.emacs.d/elpa/org-9.2.2/)
The error-message with 9.2.1-33 is this:
org-agenda-get-restriction-and-command: Wrong number of arguments
The emacs-config is the same between org-mode-versions.
Well, just uninstalled org 9.2.1, falling back to org 9.1.9 (built-in), and that fixed it. Agenda scrapes the files, no errors.
Not sure what the problem with 9.2.1. is.
I had this problem on a new install of spacemacs in mac osx. Recompiling elpa fixed it:
M-: (byte-recompile-directory package-user-dir nil 'force)
Related
I am trying to get Common Lisp running on my Windows 10 machine and I have run into a problem with getting ASDF/(ql:quickload "...") to load a project. I generated the given project with the following command (after creating a C:\Users\ig88t\src\lisp folder):
(ql:quickload "quickproject")
(quickproject:make-project "~/src/lisp/swatchblade/" :depends-on '(vecto hunchentoot))
Which correctly generates the project and I can view the source at ~/src/lisp/swatchblade.
But I am unable to load it via
(ql:quickload "swatchblade")
Instead of loading, I get an error saying
System "swatchblade" not found [Condition of type
QUICKLISP-CLIENT:SYSTEM-NOT-FOUND]
I am going by two manuals, one that Xach wrote and another tailored for Windows. Xach recommends ~/.config/common-lisp/source-registry.conf.d/projects.conf whereas the second recommends ~/.config/common-lisp/source-registry.conf.d/asdf.conf. I am currently using the version Xach wrote as it has worked for me on Linux.
Going by the manual for ASDF it seems that ~/AppData/Local/ is where I should store .config/common-lisp/source-registry.conf.d/projects.conf. I have tried storing it at ~/AppData/Local/config/... as well as ~/AppData/Local/.config/... to no avail. I noticed that Clozure CL installs some quicklisp data in ~/AppData/Local/common-lisp, so I tried putting the source-registry.conf.d folder there as in ~/AppData/Local/common-lisp/source-registry.conf.d/projects.conf as well but it didn't work.
I have tried a lot of different variations of placing the folder in different places but I have not managed to figure out the right one. I would really appreciate any help/suggestions by anyone using Common Lisp and Quicklisp on Windows.
I am using Clozure CL, 1.11.5, and the wx86cl64 binary which comes with ASDF version 3.1.5 in case that matters.
--- edit ---
After talking with Xach about this issue, I tried:
(quickproject:make-project "~/quicklisp/local-projects/swatch"
:depends-on '(vecto hunchentoot))
and then ran:
(ql:register-local-projects)
but upon running:
(ql:quickload "swatch")
it failed yet again with:
System "swatch" not found [Condition of type
QUICKLISP-CLIENT:SYSTEM-NOT-FOUND]
He said it might be related to this PR for quickproject.
--- edit #2 ---
I recently tried using SBCL and things seemed to be working. I could create projects using quickproject and load them. Note that I am unable to load projects created with quickproject under CCL. However, when I restart slime/emacs, I am unable to load any projects previously created under SBCL.
; SLIME 2.20
CL-USER> (ql:quickload "quickproject")
To load "quickproject":
Load 1 ASDF system:
quickproject
; Loading "quickproject"
("quickproject")
CL-USER> (quickproject:make-project "~/quicklisp/local-projects/test/"
:depends-on '(vecto))
"test"
CL-USER> (ql:quickload "test")
To load "test":
Load 1 ASDF system:
test
; Loading "test"
[package test]
("test")
CL-USER>
--- intermission... restarting slime ---
; SLIME 2.20
CL-USER> (ql:quickload "test")
; Evaluation aborted on #<QUICKLISP-CLIENT:SYSTEM-NOT-FOUND {10034555B3}>.
CL-USER>
So I have no clue what could be causing the issue or how to resolve it, but it appears that creating/loading projects never works under Clozure CL and to works only within the current session in SBCL.
--- edit #3 ---
It seems I was wrong about SBCL. It seems that when I run
(quickproject:make-project "~/quicklisp/local-projects/test/"
:depends-on '(vecto))
It creates a folder in C:\Users\ig88t\AppData\Roaming\quicklisp\local-projects and not in C:\Users\ig88t\quicklisp\local-projects. It can load projects created within the current session as I said earlier, but is unable to find them in a new session.
(asdf::user-source-registry :direction :output)
I'm getting the following during the bundle resources copying phase in xcodebuild (XCode 7.1):
2015-11-03 22:16:28.218 xcodebuild[28202:300463] DVTAssertions:
Warning in
/Library/Caches/com.apple.xbs/Sources/IDEXcode3ProjectSupport/IDEXcode3ProjectSupport-9061/Xcode3Core/LegacyProjects/Frameworks/DevToolsCore/DevToolsCore/BuildSystem/Runtime/PBXTargetBuildContext.mm:739
Details: unexpected successful exit code from cancelled command
<C0505:'CpResource Foo.json':P10> Object: <PBXTargetBuildContext:
0x7faec015a440> Method:
-createCommandInvocationRecordFromInvocation: Thread: <NSThread: 0x7faebc8cc070>{number = 10, name = (null)} Please file a bug at
http://bugreport.apple.com with this warning message and any useful
information you can provide.
I have ~170 items I'm copying, but for some reason a few of them give me this error.
EDIT - I just ran the command again and now it works, so it doesn't seem deterministic.
The issue was a duplicate folder in the Copy Bundle Resources section. It used to be two different files, but they were moved so XCode decided to change them both to the folder they got moved into. Go figure.
Had this issue a couple of months ago. Today that error made it's comback.
I have it only if I try to emulate from ionic (--livereload) on a iOS-Device. Seem like if you have Xcode running it occurs. Close Xcode. That fixes it.
I am trying to make leiningen work. I am using Windows 7. When I run in the command window
C:\lein new app my-app
I get the following error. Does anyone know what this means and where the error is occuring?
There is an explanation of the error message here but I did not understand if there is a fix or what causes the error.
C:\Users\a\work>lein new app my-app
java.lang.UnsupportedOperationException: nth not supported on this type: Symbol
at clojure.lang.RT.nthFrom(RT.java:857)
at clojure.lang.RT.nth(RT.java:807)
at leiningen.core.project$dep_key.invoke(project.clj:175)
at leiningen.core.project$reduce_dep_step.invoke(project.clj:183)
at clojure.lang.ArrayChunk.reduce(ArrayChunk.java:58)
at clojure.core.protocols$fn__6041.invoke(protocols.clj:98)
at clojure.core.protocols$fn__6005$G__6000__6014.invoke(protocols.clj:19
)
at clojure.core.protocols$seq_reduce.invoke(protocols.clj:31)
at clojure.core.protocols$fn__6024.invoke(protocols.clj:60)
at clojure.core.protocols$fn__5979$G__5974__5992.invoke(protocols.clj:13
)
at clojure.core$reduce.invoke(core.clj:6177)
at leiningen.core.project$meta_merge.invoke(project.clj:391)
at clojure.core$merge_with$merge_entry__4279.invoke(core.clj:2698)
at clojure.core$reduce1.invoke(core.clj:896)
at clojure.core$merge_with$merge2__4281.invoke(core.clj:2701)
at clojure.core$reduce1.invoke(core.clj:896)
at clojure.core$reduce1.invoke(core.clj:887)
at clojure.core$merge_with.doInvoke(core.clj:2702)
at clojure.lang.RestFn.invoke(RestFn.java:439)
at leiningen.core.project$meta_merge.invoke(project.clj:395)
at leiningen.core.project$apply_profiles$fn__1009.invoke(project.clj:417
)
at clojure.lang.ArrayChunk.reduce(ArrayChunk.java:58)
at clojure.core.protocols$fn__6041.invoke(protocols.clj:98)
at clojure.core.protocols$fn__6005$G__6000__6014.invoke(protocols.clj:19
)
at clojure.core.protocols$seq_reduce.invoke(protocols.clj:31)
at clojure.core.protocols$fn__6026.invoke(protocols.clj:54)
at clojure.core.protocols$fn__5979$G__5974__5992.invoke(protocols.clj:13
)
at clojure.core$reduce.invoke(core.clj:6177)
at leiningen.core.project$apply_profiles.invoke(project.clj:415)
at leiningen.core.project$init_profiles.doInvoke(project.clj:603)
at clojure.lang.RestFn.invoke(RestFn.java:425)
at leiningen.core.main$_main$fn__1332.invoke(main.clj:257)
at leiningen.core.main$_main.doInvoke(main.clj:252)
at clojure.lang.RestFn.invoke(RestFn.java:436)
at clojure.lang.Var.invoke(Var.java:423)
at clojure.lang.AFn.applyToHelper(AFn.java:167)
at clojure.lang.Var.applyTo(Var.java:532)
at clojure.core$apply.invoke(core.clj:617)
at clojure.main$main_opt.invoke(main.clj:335)
at clojure.main$main.doInvoke(main.clj:440)
at clojure.lang.RestFn.invoke(RestFn.java:482)
at clojure.lang.Var.invoke(Var.java:431)
at clojure.lang.AFn.applyToHelper(AFn.java:178)
at clojure.lang.Var.applyTo(Var.java:532)
at clojure.main.main(main.java:37)
C:\Users\a\work
As requested, here's my comment transferred into an answer. I suggested reinstalling Leiningen because apparently a broken Leiningen installation was the source of the problem.
As a little background explanation, I'm using Leiningen on both Linux and Windows, and I've made the experience myself that the primary method for installing Leiningen recommended on its homepage, the lein resp. lein.bat script, just works, whereas the alternative
installation methods (Linux package managers, Windows installer) often produce broken installations.
I think it's highly unlikely that this is essentially a leiningen error, since I can reproduce it without leiningen being involved in any way:
user=> (let [[foo bar] :froboz] (list foo bar))
UnsupportedOperationException nth not supported on this type: Keyword clojure.lang.RT.nthFrom (RT.java:857)
I spent the afternoon trying to get the ritz-swank package to work with emacs and Clojure. (Googling the error message and much more gave no useful leads.) I hope somebody can give me some pointers that'll get me up and running.
The error is Symbol's value as variable is void: slime-ritz.
According to http://www.delorie.com/gnu/docs/elisp-manual-21/elisp_142.html:
"If you have never given a symbol any value as a global variable, we say that that symbol's global value is void. In other words, the symbol's value cell does not have any Lisp object in it. If you try to evaluate the symbol, you get a void-variable error rather than a value.... A void variable does not have any value."
I tried to find the value of slime-ritz, using Emacs 'describe-variable' (C-h v), but it didn't return anything. Doing an appropos search on "ritz" turned up nothing, but searching for "slime" returned bunches of functions (so I assume that the slime package is present).
My installation procedure
I followed the instructions in the Install section of https://github.com/pallet/ritz/tree/develop/swank (the pallet/ritz project page), starting from scratch twice to make sure I was doing things right. Here is the sequence of my last attempt:
Began with a system containing neither Emacs nor a ~/.emacs.d directory.
Installed Emacs 24.2, the latest available Mac OS X version (from http://emacsformacosx.com/)
Installed Emacs Prelude through a curl command (see http://batsov.com/prelude/)
Downloaded (as the project page said to) specific versions of slime and slime-ritz
Installed both of them manually using M-x package-install-file
Exited and relaunched emacs, just in case....
Installed lein-ritz as per the page's instructions and successfully got:
Greggs-Mac-Pro:combolock gr$ lein ritz
user=> Swank server listening on local port 51521
M-x slime-connect (which is supposed to make the connection from Emacs to the Swank server) returned the error Symbol's value as variable is void: slime-ritz in the Emacs minibuffer.
Diagnostic data
Running M-x package-activated-list produced the following list of loaded packages:
(ace-jump-mode ack-and-a-half elisp-slime-nav exec-path-from-shell expand-region flycheck gist gh guru-mode helm-projectile helm logito magithub magit melpa paredit pcache projectile dash rainbow-delimiters rainbow-mode s slime slime-ritz solarized-theme undo-tree volatile-highlights yasnippet zenburn-theme)
Running M-x package-list-packages listed the following packages as installed:
ace-jump-mode 20121104....
ack-and-a-half 20130204....
dash 20130223....
elisp-slime-nav 20130127....
exec-path-from-... 20121108.945
expand-region 20130223....
flycheck 20130223....
gh 20121231.208
gist 20121231.212
guru-mode 20121016....
helm 20130223....
helm-projectile 20130131....
logito 20120225....
magit 20130222....
magithub 20121130....
melpa 20120202....
paredit 20110508....
pcache 20120408....
projectile 20130220....
rainbow-delimiters 20120428.45
rainbow-mode 0.6
s 20130216....
slime 20101113.1 <-- manually installed, from sources
slime-ritz 0.6.0 <-- specified by pallet/ritz page
solarized-theme 20130215....
undo-tree 20130119.926
volatile-highli... 20120215.9
yasnippet 20130218....
zenburn-theme 20130215....
I noticed that clojure-mode wasn't present, so I added that, but step 8, above, gave the same error message.
Some shot-in-the-dark questions
1) Do I need to install pallet?
2) Do I need to install any other package from the ritz family (https://github.com/pallet/ritz)?
I'm really looking forward to using ritz-swank--it looks really powerful! (Thanks to Hugo Duncan for all the hard work!)
Emacs Predule ships nrepl.el instead of swank-clojure. You need to install nrepl-ritz instead of swank-ritz. Swank-clojure is a dead project, that's no longer supported in clojure-mode 2.0.0 (the one that comes with Predule).
I'd like to start Emacs on Mac OS X.
When I run 'emacs' comamnd in terminal, I got the error;
signal(error ("Unknown keyword :risky"))
error("Unknown keyword %s" :risky)
custom-handle-keyword(package-load-list :risky t custom-variable)
...
..
What is the 'risky'?
I just install 'Starter Kit'.
How I solve this problem?
===== UPDATE
This error only occure in Built-in Emacs on Mac OSX Terminal.
In GUI Emacs(GNU), It works.
Here is full trace of error.
Debugger entered--Lisp error: (error "Cannot return from the debugger in an error")
signal(error ("Unknown keyword :risky"))
error("Unknown keyword %s" :risky)
custom-handle-keyword(package-load-list :risky t custom-variable)
custom-declare-variable(package-load-list (quote (all)) "List of packages for `package-initialize' to load.\nEach el$
(defcustom package-load-list (quote (all)) "List of packages for `package-initialize' to load.\nEach element in this$
eval-buffer(#> nil "/Users/rushcut/.emacs.d/package.el" nil t) ; Reading at buffer position 9123
load-with-code-conversion("/Users/rushcut/.emacs.d/package.el" "/Users/rushcut/.emacs.d/package.el" nil t)
require(package)
eval-buffer(# nil "/Users/rushcut/.emacs.d/init.el" nil t) ; Reading at buffer position 1099
load-with-code-conversion("/Users/rushcut/.emacs.d/init.el" "/Users/rushcut/.emacs.d/init.el" t t)
load("/Users/rushcut/.emacs.d/init" t t)
#[nil "^H\205\276^# \306=\203^Q^#\307^H\310Q\202A^# \311=\2033^#\312\307\313\314#\203#^#\315\202A^#\312\307\313\31$
command-line()
normal-top-level()
===== FINALLY
Install emacs 23.2.
Everything works fine.
Remove the starter kit, start fresh.
As harpo commented, to debug your actual problem, try starting Emacs with --debug-init, which should provide a stack trace showing what line caused the problem.
But really, get rid of the starter kit.
If you want to start using Emacs, check out all the other questions folks have asked about beginning Emacs and try some of the tips for beginners folks have already given. Of particular interest is a question about starting with Ergo Emacs, which is essentially the same thing as starting off with the Starter Kit.
UPDATE
From your stack trace, it looks as though the version of custom that the starter kit expects is newer than the version shipped with the Emacs you're using on the Mac. The risky is a keyword for defcustom, which was added in Emacs 23.1 (see NEWS.23.1). So, either upgrade your Mac's Emacs, download a newer version of custom (may not be possible at this point), or remove the starter kit by commenting out (require 'package) in your .init.el.