Symbol's function definition is void: org-projectile-per-project

[lsytj0413]

Description :octocat:

Error (use-package): org-projectile :config: Symbol's function definition is void: org-projectile-per-project

Reproduction guide :beetle:

• Start Emacs

Observed behaviour: :eyes: :broken_heart: in the Warnings buffer shows: Error (use-package): org-projectile :config: Symbol's function definition is void: org-projectile-per-project

Expected behaviour: :heart: :smile:

System Info :computer:

• OS: gnu/linux
• Emacs: 24.5.1
• Spacemacs: 0.200.9
• Spacemacs branch: develop (rev. a0cdcca)
• Graphic display: t
• Distribution: spacemacs
• Editing style: vim
• Completion: helm
• Layers:

  (helm
  (auto-completion :variables auto-completion-enable-sort-by-usage t)
  (better-defaults :variables better-defaults-move-to-end-of-code-first t)
  emacs-lisp git markdown org
  (shell :variables shell-default-shell 'multi-term shell-default-height 30 shell-default-position 'bottom)
  (c-c++ :variables c-c++-default-mode-for-headers 'c++-mode c-c++-enable-clang-support t)
  asm
  (python :variables python-sort-imports-on-save t)
  javascript github semantic
  (go :variables go-tab-width 4 go-use-gometalinter t)
  ranger gtags ibuffer sql
  (colors :variables colors-enable-nyan-cat-progress-bar t colors-enable-rainbow-identifiers t)
  (spacemacs-layouts :variables layouts-enable-autosave t layouts-autosave-delay 300)
  graphviz plantuml docker
  (syntax-checking :variables syntax-checking-enable-by-default t)
  liter ycmd)

Backtrace :paw_prints:

[dre-hh]

had same issue, but newest spacemacs pull from develop and package update solved it

[lsytj0413]

@dre-hh I have pull from develop branch since the commit #98ff30, and the problem is still exsit.

[dre-hh]

@lsytj0413 but what about updating emacs packages?

[yatesco]

It seems org-projectile has undergone some significant internal redesign with some breaking changes. The front page (https://github.com/IvanMalison/org-projectile) gives more info, as does this issue: https://github.com/IvanMalison/org-projectile/issues/31

[incandescentman]

Same issue here. Switched to develop and it seems to be fixed for now.

Symbol's function definition is void:
(org-projectile:per-repo)
 (org-projectile:per-repo)
 (if (file-name-absolute-p org-projectile-file) (progn (setq...

[lsytj0413]

@dre-hh @incandescentman I use the develop branch and update all packages, but the issue is still exsit. BUT when i switch to MASTER branch then the issue has gone.

[d12frosted]

org-projectile-per-project is defined in latest org-projectile.

[lsytj0413]

I update org-projectile to:

org-projectile-20170803.634

and when i start spacemacs, there is a warning:

Error (use-package): org-projectile :init: Symbol's value as variable is void: occ-get-categories

[bnicenboim]

Hi, I've just installed spacemacs (never used emacs or vim before, just sublime). Is there a workaround? I've actually installed spacemacs to use org-mode.

[lsytj0413]

@bnicenboim the newest version has solve this problem, you can update org-projectile package to the newest version. Other way, you can add org-projectile to the dotspacemacs-exclude-packages list.

[lazysquid]

@lsytj0413 I've installed the newest version but it still has same problem. I'm using master branch of spacemacs.

[lsytj0413]

@FrostedPenguin I'm using the develop branch

[channingwalton]

Hi, any further updates on this issue?

[lsytj0413]

@channingwalton No updates.

[peterhoeg]

Isn't it a bit premature to close the issue as it persists?

[yatesco]

Any idea when this will make it to the master branch?

[lsytj0413]

@yatesco Maybe add org-projectile to the dotspacemacs-exclude-packages list.

[yatesco]

Thanks @lsytj0413 - I realise I could exclude it :-), but I was hoping there would be a fix. The more I read about org in spacemacs the more I appreciate the complexities involved otherwise I guess a simple cherry-pick would be possible.

In this case a git checkout develop is the answer I think.

[jonathanunderwood]

Still seeing this today - I am confused as to why the issue was closed without a solution?

[chriskaukis]

Experiencing this same error. Fresh install from master to confirm.

[prajnak]

also confirming the same error on a fresh install from master

[bricewge]

As said before, this issue is fixed in develop. If you want to stay on 0.200.9 you can cherry-pick 6063466231; it fix the issue.

[jonathanunderwood]

Why not make a fixed release from master, rather than leaving this broken?

On 14 Oct 2017 15:18, "bricewge" notifications@github.com wrote:

As said before, this issue is fixed in develop. If you want to stay on 0.200.9 you can cherry-pick 6063466 https://github.com/syl20bnr/spacemacs/commit/6063466231ce5e209aacd2de612e53390a25c442; it fix the issue.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/syl20bnr/spacemacs/issues/9374#issuecomment-336637753, or mute the thread https://github.com/notifications/unsubscribe-auth/AA8jcg7K0WTPEDxlJutCIISabodFArgcks5ssMLQgaJpZM4Oumz7 .

[Kingpatzer]

I'm a brand new user to spacemacs and I'd like to understand how to fix this issue. Note: I don't want to run the development branch because I don't want other things breaking and I don't know what "cherry picking" that bricwge is mentioning means -- but it looks like he is suggesting hand coding a bunch of changes to files -- which for someone who's using Emacs and org mode for doing papers and running a few python data scripts is really asking a lot.

How does a normal, everyday non-hacker fix this problem on the main release?

I've deleted the package from ~/.emacs.d/elpa and let spacemacs re-install, but that doesn't seem to do it.

[peterhoeg]

@Kingpatzer, you can add org-projectile to dotspacemacs-excluded-packages on your $HOME/.spacemacs/init.el file as mentioned in https://github.com/syl20bnr/spacemacs/issues/9374#issuecomment-325238803.

[cypa]

issue persists

[jonathanunderwood]

Still broken on the release (master) branch today. @syl20bnr: why not backport the fix to master so it's released to end users?

[00krishna]

I ran into the same exact issue, with this error showing up on startup. I am on the MASTER branch and here is what worked for me.

0. Close emacs. I use version 25.3
1. I went into the ~/.emacs.d/elpa directory
2. Searched for org-projectile
3. Deleted the org-projectile-xxx folder
4. Then restart emacs and it will download org-projectile again.

So this helped fix my issue. I had to try this a couple of times before it finally worked. Hope this helps.

[stevexyc]

To fix this issue, I went into

1. cd ~/.emacs.d/elpa/org-projectile-XXXX
2. git fetch
3. restart emacs Should solve the problem

[ghost]

Fresh install of spacemacs today, and hit this problem. What's blocking a fix for this being pushed to master?

[macbem]

Issue persists

[rebcabin]

find ~/.emacs.d -name "*.elc" -delete

restart emacs

[nocksock]

I still have this exact same issue. Has it been solved?

[venturno]

Just had this same issue today as well. Using @stevexyc 's git fetch suggestion worked for me

[SwenChan]

Same issue, and thx to @stevexyc 's suggestion, it work for me, too. But curiously, why?

[kelanwu]

This issue still persists in master(0.200.13), but has fixed in develop branch. I'd like to stay in master branch, and I solved this by @bricewge 's suggestion.

[nocksock]

Tried @bricewge's suggestion and it worked for me too. In a nutshell: git cherry-pick 6063466231ce5e209aacd2de612e53390a25c442 in the ~/.emacs.d repository. Restart emacs and all org-projectile commands work as intended 🎉

[frankjonen]

Hmm, not quite. Going into ~/.emacs.d and executing git cherry-pick 6063466231ce5e209aacd2de612e53390a25c442 yields:

error: could not apply 60634662... Makeorg-projectileintegration compatible with its new version hint: after resolving the conflicts, mark the corrected paths hint: with 'git add <paths>' or 'git rm <paths>' hint: and commit the result with 'git commit'

The only result I got was that the start screen stopped listing my projects and I have to reinstall now.

After the re-install I tried @stevexyc's approach. It did nothing. I still get Error (use-package): org-projectile/:config: Symbol’s function definition is void: org-projectile:per-repo when I C-c c

[ginhton]

I solved this problem by using following solutions (in evil mode):

1. SPC h SPC, input "org" , and then select layer -> org. press Enter.
2. SPC f j, select "package.el" and press Enter to open that file.
3. /org-projectile:per-repo, find that line and g c c or just comment this line.
4. restart spacemacs.

original link - Chinese

[rlcintra]

Please reopen this issue since it still affects the master branch (release 0.200.13.x).

[anhdle14]

Fresh install of emacs is still being affected.

Spacemacs v.0.200.13

[ghost]

After a fresh Emacs upgrade and reinstall of space macs I faced same issue with following setup:

• OS: debian
• Emacs: 25.1.1
• Spacemacs: 0.200.13

Turns out it was easy as deleting .emacs.d/elpa directory and restarting emacs.

[jbhannah]

There are multiple function calls in Spacemacs' org integration that have been renamed in org-projectile, e.g. org-projectile:per-repo is now org-projectile-per-project, in both the MELPA stable and MELPA latest releases. I'm planning on going through and fixing these references and opening a PR. This is fixed in https://github.com/syl20bnr/spacemacs/commit/6063466231ce5e209aacd2de612e53390a25c442 in the develop branch.

[MrMic]

Same issue today, with a new install of spacemacs.

[elatomo]

I also faced this issue today after updating all packages.

find ~/.emacs.d/elpa -name "*elc" -delete and restarting fixed it.

[gavinrogers]

Error (use-package): org-projectile/:config: Symbol’s function definition is void: org-projectile:per-repo

Still happening on master. I switched to dev yesterday which didn't fix it, but following the directions given by @stevexyc above seemed to work but today I'm seeing the error again.

[acgollapalli]

Replacing:

(with-eval-after-load 'org-agenda
  (require 'org-projectile)
  (push (org-projectile:todo-files) org-agenda-files))

with:

(require 'org-projectile)
(setq org-agenda-files (append org-agenda-files (org-projectile-todo-files)))

in my config seems to fix it on develop. The symbols in the org layer are outdated on master.

[jink-e]

I download the last master, when emacs start, get a new error as below: Error (use-package): projectile/:config: Symbol’s function definition is void: projectile-global-mode env: windows 10 emacs 26.1 emacs-w64-25.3-O2-with-modules

[sdwolfz]

@Ryuk03 Your issue is fixed on develop. You can either switch to that branch or enable spacepla in your .spacemacs so that you get an older/stable version of projectile.

[colonelrascals]

This still affects the master branch correct?