Error In Process Filter Wrong Type Argument Stringp Nil

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of emacs wrong type argument stringp this site About Us Learn more about Stack Overflow the company Business emacs stringp Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask wrong type argument stringp t Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up

Emacs Wrong Type Argument Number-or-marker-p Nil

Wrong type argument: stringp, nil error up vote 5 down vote favorite I need to use update-directory-autoloads function in a little el-script. When I'm trying to call this function with an argument that is a name of a directory I receive this error: Wrong type argument: stringp, nil. Call looks like this: (update-directory-autoloads "~/test") emacs elisp share|improve this question edited Feb 7 '13 emacs wrong type argument arrayp nil at 22:31 Jesus Ramos 18.1k53971 asked Feb 7 '13 at 22:14 Jauhien Piatlicki 148111 add a comment| 2 Answers 2 active oldest votes up vote 5 down vote accepted Generating autoload files is poorly documented. You're experiencing the problem that arises because you haven't set the variable generated-autoload-file. Try the following: (let ((generated-autoload-file "~/test/loaddefs.el")) (update-directory-autoloads "~/test")) Update the generated-autoloads-file binding to be the location where you want the loaddefs.el file to live. share|improve this answer answered Feb 7 '13 at 22:41 Trey Jackson 59.9k8150190 Thank you. The problem really was in generated-autoload-file undefined. –Jauhien Piatlicki Feb 7 '13 at 23:59 add a comment| up vote 9 down vote When you get Wrong type argument: foo, bar., you should M-: (setq debug-on-error t) RET and then reproduce the error so as to get a backtrace. Actually, you can set debug-on-error like that in your .emacs and Emacs usually stays perfectly useable. share|improve this answer answered Feb 8 '13 at 2:40 Stefan 19.7k12049 6 M-x toggle-debug-on-error is a bit nicer for the interactive case. –phils Feb 8 '13 at 5:45 Indeed. Or even

Sign in Pricing Blog Support Search GitHub This repository Watch 56 Star 810 Fork 115 jorgenschaefer/elpy Code Issues 199 Pull requests 7 Projects 0 Wiki Pulse Graphs New issue error in process filter: Wrong type argument: stringp, nil emacs debug on error #355 Closed birkenfeld opened this Issue Sep 11, 2014 · 6 comments Projects None yet

Emacs Debugger

Labels bug Reported upstream Milestone v1.6 Assignees No one assigned 2 participants birkenfeld commented Sep 11, 2014 Typing "from"

Spacemacs Windows

in a Python module, I get this "signal"ed in the echo area, and the message log contains error in process filter: if: Wrong type argument: stringp, nil error in process filter: Wrong type argument: stringp, nil This http://stackoverflow.com/questions/14762036/wrong-type-argument-stringp-nil-error comes from elpy-rpc--default-error-callback (the first branch) I would ignore it, but the signal causes a 2-second "freeze" of Emacs, so it gets very annoying. Do you have a pointer on how to debug where the error actually is generated? I'm a bit lost in the many levels of RPC indirection :) birkenfeld commented Sep 11, 2014 Got it: it actually comes from company, the call of company-dabbrev-code in elpy-company-backend. Backtrace here: http://ix.io/ehN I guess https://github.com/jorgenschaefer/elpy/issues/355 I'll also report this to company-mode, don't know if you want to add a try-catch around the call... Owner jorgenschaefer commented Sep 11, 2014 Thank you for the report! Does M-: (company-dabbrev-code 'candidate "from") throw the same error for you? If so, what version of company are you using? jorgenschaefer added the bug label Sep 11, 2014 jorgenschaefer added this to the v1.6 milestone Sep 11, 2014 birkenfeld commented Sep 11, 2014 Yep, same error. It's company 0.8.3, I've reported to Dmitry here: company-mode/company-mode#183 -- it's a bit mysterious... By the way, thank you so much for elpy. It's so nice to have these loose features all bundled up in a nice package. jorgenschaefer added the Reported upstream label Sep 11, 2014 Owner jorgenschaefer commented Sep 11, 2014 Thank you for reporting this upstream. I can't reproduce this locally with company 0.8.3. Hm. Weird. birkenfeld commented Sep 11, 2014 Turns out it was a rogue package in my lisp library, so not a bug. Sorry to bother you. birkenfeld closed this Sep 11, 2014 Owner jorgenschaefer commented Sep 11, 2014 Thank you for the nice bughunting and for the kind words – enjoy Elpy. :-) Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Contact GitHub API Training Shop Blog About ©

Sign in Pricing Blog Support Search GitHub This repository Watch 153 Star 1,919 Fork https://github.com/clojure-emacs/cider/issues/1608 333 clojure-emacs/cider Code Issues 79 Pull requests 2 Projects 0 Wiki Pulse Graphs New issue C-c C-t C-t on deftest form can cause stringp, nil type error #1608 Closed RickMoynihan opened this Issue Mar 7, 2016 · 3 comments Projects None yet Labels None yet Milestone No milestone wrong type Assignees No one assigned 3 participants RickMoynihan commented Mar 7, 2016 When running a test with C-C C-t C-t with the cursor inside a deftest form an error occurs. Expected behavior Tests should run and return success or failure message/report. Actual behavior error in process filter: cider-propertize: Wrong type wrong type argument argument: stringp, nil error in process filter: Wrong type argument: stringp, nil With toggle-debug-on-error Debugger entered--Lisp error: (wrong-type-argument stringp nil) propertize(nil face font-lock-type-face) cider-propertize(nil ns) cider-test-echo-summary((dict "error" 0 "fail" 0 "ns" 1 "pass" 0 "test" 0 "var" 1) (dict)) #[257 "\306�\307\"\306�\310\"\306�\311\"\306�\312\"\306�\313\"\314�\235\203$ Steps to reproduce the problem Some deftests work others don't. I'm not sure exactly when this occurs, but I think it might happen when a test includes a failing test who's is call is in another namespace. Put cursor on a deftest form where the error occurs Run C-C C-t C-t. CIDER version information CIDER 0.11.0 (Clojure 1.8.0, nREPL 0.2.12) Emacs version E.g. 24.4.1 Operating system OSX 10.9.5 jeffvalk commented Mar 7, 2016 if you have a minimal repro case, please post that code. clojure-emacs member bbatsov commented Mar 9, 2016 Seems the ns is nil for some reason. jeffvalk commented Mar 9, 2016 This is a duplicat