Emacsclient *error* Wrong Type Argument Stringp Nil

Sign in Pricing Blog Support Search GitHub This repository Watch 127 Star 2,295 Fork 432 magit/magit Code Issues 20 Pull requests 3 emacs wrong type argument stringp nil Projects 0 Wiki Pulse Graphs New issue Cannot commit with new commit cedet wrong type argument stringp nil workflow: wrong-type-argument stringp, nil #772 Closed zachallaun opened this Issue Aug 19, 2013 · 16 comments Projects None yet Labels emacsclient Milestone 2.1.0 Assignees No one assigned 4 participants zachallaun commented Aug 19, 2013 Hi there, I've just upgraded magit and am running into an error when trying to commit: wrong-type-argument stringp, nil. Everything was previously working with the old-style commit workflow (c immediately dropping you into a log buffer, etc). I've confirmed that committing also fails in a brand-new git repo, but I'm not sure where to go from here. The exact operations that lead to the error: M-x magit-status s to stage a file c to begin commit c to commit without any options -- this causes the error Backtrace: Debugger entered--Lisp error: (wrong-type-argument stringp nil) file-name-directory(nil) magit-commit(nil) call-interactively(magit-commit) magit-key-mode-command(magit-commit) (lambda nil (interactive) (magit-key-mode-command (quote magit-commit)))() call-interactively((lambda nil (interactive) (magit-key-mode-command (quote magit-commit))) nil nil) command-execute((lambda nil (interactive) (magit-key-mode-command (quote magit-commit)))) Magit member tarsius commented Aug 19, 2013 Let me guess you are on OS X? Any ways just pushed a quick fix. Magit member tarsius commented Aug 19, 2013 But then you might run into #770. zachallaun commented Aug 19, 2013 Thanks for the quick fix! Not sure if there's more to be done, but if not, feel free to close. vermiculus commented Aug 19, 2013 Still doesn't work for me on Windows 8. (At least, not with the most current MELPA build. I'll confirm that it doesn't work early tomorrow/in a few hours.) I narrowed the issue down a bit: (magit-with-git-editor-setup magit-server-window-for-commit (apply 'magit-run-git-async "commit" magit-custom-options)) Executing this inside my magit-status buffer (with toggle-debug-on-error) yeilds Debugger entered--Lisp error: (wrong-type-argument stringp nil) fil

file Date: Wed, 01 Jun 2016 16:10:49 -0300 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.94 (berkeley-unix) Hi, After starting an Emacs daemon, everything works as expected, but after some time (or event I'm unaware of), trying to open a file from a shell gives an error. % emacsclient some_file Waiting for Emacs... *ERROR*: Wrong type argument: stringp, nil I can create new frames, so the daemon is alive and reachable, but https://github.com/magit/magit/issues/772 the error is still reported. % emacsclient -nc *ERROR*: Wrong type argument: stringp, nil (new frame opens) Creating a new frame without the -n flag fails. % emacsclient -nc *ERROR*: Wrong type argument: stringp, nil (no new frame) How should I debug this? Using (setq debug-on-error t) doesn't help. This https://lists.gnu.org/archive/html/emacs-devel/2016-06/msg00003.html is with the 5th pretest for 25, but the problem has been around earlier in the 25 branch. Regards, Joseph signature.asc Description: PGP signature reply via email to [Prev in Thread] Current Thread [Next in Thread] emacsclient in 25 branch: error opening any file, Joseph Mingrone<= Re: emacsclient in 25 branch: error opening any file, Joseph Mingrone, 2016/06/01 Re: emacsclient in 25 branch: error opening any file, Eli Zaretskii, 2016/06/04 Re: emacsclient in 25 branch: error opening any file, Joseph Mingrone, 2016/06/05 Re: emacsclient in 25 branch: error opening any file, Live System User, 2016/06/05 Prev by Date: Re: [Emacs-diffs] master a76420c: Fix emacs-repository-get-version with packed .git Next by Date: Re: emacsclient in 25 branch: error opening any file Previous by thread: Re: [Emacs-diffs] master a76420c: Fix emacs-repository-get-version with packed .git Next by thread: Re: emacsclient in 25 branch: error opening any file Index(es): Date Thread

here for a quick overview of the site Help Center Detailed answers to any questions you http://stackoverflow.com/questions/14762036/wrong-type-argument-stringp-nil-error might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting http://emacs.1067599.n5.nabble.com/emacsclient-in-25-branch-error-opening-any-file-tp399273.html ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 wrong type million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up 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 wrong type argument 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 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.

threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ emacsclient in 25 branch: error opening any file Hi, After starting an Emacs daemon, everything works as expected, but after some time (or event I'm unaware of), trying to open a file from a shell gives an error. % emacsclient some_file Waiting for Emacs... *ERROR*: Wrong type argument: stringp, nil I can create new frames, so the daemon is alive and reachable, but the error is still reported. % emacsclient -nc *ERROR*: Wrong type argument: stringp, nil (new frame opens) Creating a new frame without the -n flag fails. % emacsclient -nc *ERROR*: Wrong type argument: stringp, nil (no new frame) How should I debug this? Using (setq debug-on-error t) doesn't help. This is with the 5th pretest for 25, but the problem has been around earlier in the 25 branch. Regards, Joseph signature.asc (834 bytes) Download Attachment Joseph Mingrone Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: emacsclient in 25 branch: error opening any file Joseph Mingrone <[hidden email]> writes: > After starting an Emacs daemon, everything works as expected, but after some > time (or event I'm unaware of), trying to open a file from a shell gives an > error. > % emacsclient some_file Waiting for Emacs... *ERROR*: Wrong type argument: > stringp, nil > I can create new frames, so the daemon is alive and reachable, but the error > is still reported. > % emacsclient -nc *ERROR*: Wrong type argument: stringp, nil (new frame opens) > Creating a new frame without the -n flag fails. > % emacsclient -nc *ERROR*: Wrong type argument: stringp, nil (no new frame) > How should I debug this? Using (setq debug-on-error t) doesn't help. > This is with the 5th pretest for 25, but the problem has been around earlier > in the 25 branch. After the problem has been triggered, this still works without an error. % emacsclient -e '(find-file "~/some_file")' signature.asc (834 bytes) Download Attachment Eli Zaretskii Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate