Skip to content
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

Develop branch: New install says No support found to parse buffer \"org-loaddefs.el\"" #2042

Closed
swaroopch opened this issue Jun 17, 2015 · 14 comments

Comments

@swaroopch
Copy link
Contributor

I get these errors:

Not enabling jit-lock: it does not work in indirect buffer
Loading semantic/db-file...done
Parsing org-loaddefs.el (LL)...
Error running timer `semantic-idle-scheduler-function': (error "No support found to parse buffer \"org-loaddefs.el\"")
Parsing org-loaddefs.el (LL)...
Idle Work Parse Error: "#<buffer org-loaddefs.el> - No support found to parse buffer \"org-loaddefs.el\""

With these layers enabled:

     auto-completion
     better-defaults
     emacs-lisp
     git
     markdown
     org
     (shell :variables
            shell-default-height 30
            shell-default-position 'bottom)
     syntax-checking
     version-control

     c-c++
     clojure
     dash
     github
     html
     osx
     python
     rust
     semantic
     sql
@Josh-Tilles
Copy link
Contributor

+1
I've been seeing the same messages

@syl20bnr
Copy link
Owner

What's your Emacs version ? I presume it comes from the semantic layer, can you test without the semantic layer ?

@swaroopch
Copy link
Contributor Author

@syl20bnr Yes, you're right, it looks like this issue happens only when semantic layer is enabled, I don't see the error on a new install without it.

syl20bnr pushed a commit that referenced this issue Aug 1, 2015
I have seen many "I have a problem" discussions in the Gitter chat which
starts with a barrage of questions "Which OS? Which Emacs version?",
etc., so I thought it may be useful to have one function that will
generate the info to be copy-pasted into the Gitter chat and hence both
the user and others helping in the Gitter chat can jump directly to
solving the problem instead of the support volley to figure out the
setup.

Example output:

ELISP> (spacemacs/system-info)
"OS: darwin Emacs: 24.5.1 Spacemacs: 0.103.0 Spacemacs branch: develop
Layers: ((auto-completion :variables auto-completion-enable-help-tooltip
t) better-defaults emacs-lisp git markdown org (shell :variables
shell-default-height 30 shell-default-position (quote bottom))
syntax-checking version-control c-c++ clojure dash github html osx
python semantic sql)"

References:

From
#2033 (comment) :

> Also what is your emacs version and OS ?

From
#2042 (comment) :

> What's your Emacs version ? I presume it comes from the semantic
layer, can you test without the semantic layer ?
@x-ji
Copy link
Contributor

x-ji commented Aug 11, 2015

I also had this error. At the same time I had another error Symbol's value as variable is void: org-planning-line-re. I disabled both org and semantic layers, and reinstalled them. Seems both errors are gone for now.

@x-ji
Copy link
Contributor

x-ji commented Aug 11, 2015

Ah no. The issue Symbol's value as variable is void: org-planning-line-re resurfaced after Spacemacs is launched next time.

@x-ji
Copy link
Contributor

x-ji commented Aug 11, 2015

Well according to discussions here, the issue Symbol's value as variable is void: org-planning-line-re is caused by using things from org before load-paths is set up. I moved all my org-related customizations from spacemacs/init () to dotspacemacs/config (), and the issues seem to be gone.

@jtmoulia
Copy link

🍻 to @x-ji -- moving org related config to dotspacemacs/config also fixed this issue for me.

@StreakyCobra
Copy link
Contributor

Do you still have this problem @swaroopch?

@swaroopch
Copy link
Contributor Author

Seems to be fixed now!

@swaroopch
Copy link
Contributor Author

Hmm, not sure what combination of layers cause this, but this just happened when I had more than just org and semantic layers:

Parsing org-loaddefs.el<org-plus-contrib-20151005> (LL)...
Error running timer `semantic-idle-scheduler-function': (error "No support found to parse buffer \"org-loaddefs.el<org-plus-contrib-20151005>\"")

This is what I actually have now:

System Info

  • OS: darwin
  • Emacs: 24.5.1
  • Spacemacs: 0.105.0
  • Spacemacs branch: develop (rev. 3fb3877)
  • Distribution: spacemacs
  • Layers:
(auto-completion better-defaults emacs-lisp git markdown org
                 (shell :variables shell-default-shell 'eshell shell-default-height 30 shell-default-position 'bottom)
                 syntax-checking version-control c-c++ clojure go html
                 (python :variables python-fill-column 99)
                 sql dash github osx semantic yaml)

@swaroopch swaroopch reopened this Nov 9, 2015
@dzannotti
Copy link

just seen this with

(auto-completion :variables
                      auto-completion-enable-snippets-in-popup t
                      auto-completion-enable-sort-by-usage t
                      auto-completion-enable-company-help-tooltip t
                      :disabled-for
                      html)
     better-defaults
    syntax-checking
     colors
     eyebrowse
     gtags
     dash
     dockerfile
     elm
     git
     evil-snipe
     org
     semantic
     markdown
     emacs-lisp
     clojure
     common-lisp
     javascript
     react
     pandoc
     php
     python
     ruby
     c-c++
     html
     haskell
     (ibuffer :variables
              ibuffer-group-buffers-by 'projects)
     shell
     shell-scripts
     search-engine
     spell-checking
     spotify
     vinegar
     xkcd
     yaml
  )

on master branch, emacs 25.5.15, osx

@jb55
Copy link
Contributor

jb55 commented Feb 9, 2016

rm -rf .cache/semanticdb fixed this for me

@swaroopch
Copy link
Contributor Author

I haven't seen this issue happen off late, so closing.

@bb4242
Copy link

bb4242 commented Oct 19, 2016

Actually, I just noticed this happening again in 0.200.3. Removing .cache/semanticdb seems to help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants