Load Fail on Emacs Snapshot 24.3.50.1

[emacs-d-mode-maintainers]

Load Fail on Emacs Snapshot 24.3.50.1

[russel]

I only have Emacs 24.3.1 on Debian Unstable, d-mode is working just fine for me. What is the E-Lisp code you have that leads to the problem?

[nordlow]

I hade forgotten that an older version where loaded by an ELPA installation. That version failed on Emacs Snapshot.

My mistake.

Sorry. I'm closing this.

[russel]

No problem. I'm glad it is a resolved problem.

[nordlow]

I'm afraid the problem has returned in Emacs git together with my settings and I don't know what made it work yesterday. I have to be more strict with me version controlling my Emacs settings. Unfortunately it doesn't occur in git snapshot with default (vanilla) settings. Here's the error

c-get-lang-constant: `c-matchers-2' got no (prior) value in d-mode (might be a cyclic reference)

And when sexp-evaluate d-mode.el line-by-line it gets stuck on the expression

(defconst d-font-lock-keywords-2 (c-lang-const c-matchers-2 d)
  "Fast normal highlighting for D mode.")

I get the same error as above.

I've put my d-mode dir as the first element in my load-path.

Ideas anyone?

In the meanwhile I'm gonna setup a Emacs lisp script that loads d-mode in the beginning then evaluates each line in my .emacs together with a reload of d-mode until the problem occurs. Patience...

I'm using lots of other language extensions and they all work fine so this might be a potential problem for other users.

[nordlow]

This problem occurrs only when I aquire d-mode through ELPA not when I clone from this github repo.

I'm closing this for now.

[russel]

I wonder if we should keep this open or create a new report: if things works using a Git clone but not as a MELPA package then there is a real problem. I was not aware this mode was in ELPA.

[KDr2]

I got this error too (installed from ELPA), @nordlow could you tell me how have you resolved this?

[russel]

@KDr2 Are you getting this from MELPA or Marmalade? Would it be possible to post a log describing the problem you are seeing?