flyingmachine / emacs-for-clojure

522 stars 267 forks source link

ido-ubiquitous-default-command-overrides #1

Closed kalse closed 10 years ago

kalse commented 10 years ago

When starting Emacs 24.3.1 (i386-mingw-nt6.1.7601) of 2013-03-17 on MARVIN on Windows (Windows 7) I receive:

Warning (initialization): An error occurred while loading `c:/Users/BohmOn/.emacs.d/init.el':

Symbol's value as variable is void: ido-ubiquitous-default-command-overrides

To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file.  Start Emacs with
the `--debug-init' option to view a complete error backtrace.

Starting with the --debug-init option produces:

Debugger entered--Lisp error: (void-variable ido-ubiquitous-default-command-overrides)
  (defvar ido-ubiquitous-command-overrides ido-ubiquitous-default-command-overrides "List of command override specifications for ido-ubiquitous\n\nEach override specification describes how ido-ubiquitous should\nbehave one or many commands. A specification has the\nform `(BEHAVIOR MATCH-TYPE MATCH-TEXT)'. BEHAVIOR is one of the\nfollowing:\n\n  * `disable': ido-ubiquitous should not be used at all for the\n    specified commands;\n  * `enable': ido-ubiquitous may be used with the specified\n    commands, without emulating the old-style default selection\n    of `completing-read';\n  * `enable-old': ido-ubiquitous may be used with the specified\n    commands, and should emulate the old-style default selection\n    of `completing-read'.\n\nMATCH-TYPE affects how MATCH-TEXT is interpreted, as follows:\n\n  * `exact': the specification only affects the one command\n    whose name is MATCH-TEXT;\n  * `prefix': the specification affects any command whose name\n    starts with MATCH-TEXT (This is useful for specifying a\n    certain behavior for an entire package);\n  * `regexp': the specification affects any command whose name\n    matches MATCH-TEXT (with MATCH-TEXT being interpreted as a\n    regular expression)\n\nMATCH-TEXT should be a string.\n\nSince this variable's has a somewhat complex structure, it is\nrecommended that you set this variable through Customize.\n\nNote that this variable only affects *commands*, which are\nfunctions marked as interactive. See\n`ido-ubiquitous-function-overrides' for how to modify the\nbehavior of ido-ubiquitous for arbitrary functions.\n\nIf you need to add a new specification to this list, please also\nfile a bug report at https://github.com/DarwinAwardWinner/ido-ubiquitous/issues")
  eval-buffer(#<buffer  *load*-311224> nil "c:/Users/BohmOn/.emacs.d/elpa/ido-ubiquitous-2.0/ido-ubiquitous-autoloads.el" nil t)  ; Reading at buffer position 5285
  load-with-code-conversion("c:/Users/BohmOn/.emacs.d/elpa/ido-ubiquitous-2.0/ido-ubiquitous-autoloads.el" "c:/Users/BohmOn/.emacs.d/elpa/ido-ubiquitous-2.0/ido-ubiquitous-autoloads.el" nil t)
  load("c:/Users/BohmOn/.emacs.d/elpa/ido-ubiquitous-2.0/ido-ubiquitous-autoloads" nil t)
  package-activate-1(ido-ubiquitous [(2 0) nil "Use ido (nearly) everywhere."])
  package-activate(ido-ubiquitous (2 0))
  package-initialize()
  eval-buffer(#<buffer  *load*> nil "c:/Users/BohmOn/.emacs.d/init.el" nil t)  ; Reading at buffer position 229
  load-with-code-conversion("c:/Users/BohmOn/.emacs.d/init.el" "c:/Users/BohmOn/.emacs.d/init.el" t t)
  load("c:/Users/BohmOn/.emacs.d/init" t t)
  #[0 "\205\262

It seems to be starter-kit's fault, because when I comment that out in the init.el the error disappears, though I didn't find any issue mentioning the ido-ubiquitous-default-command-overrides in starter-kit's repo.

My emacs version is 24.3.1 (i386-mingw-nt6.1.7601) of 2013-03-17 on MARVIN, system is Windows 7 (Professional, 64-bit).

davidglassborow commented 10 years ago

Seeing the same issue on OS X, emacs 24.3 (9.0)

tvon commented 10 years ago

This seems to be an issue with ido-ubiquitous, at least I get the same error using prelude.

flyingmachine commented 10 years ago

Thanks, and sorry for the hassle. @tvon is wright, it's an issue with ido-ubiquitous. I've updated the repo, and it should work now. I recommend removing ~/.emacs.d and starting over. If you have changes you want to keep, then you can just rm -Rf ~/.emacs.d/elpa/ido-ubiquitous-2.0 && cp -R emacs-for-clojure/elpa/ido-ubiquitous-0.7 ~/.emacs.d/elpa .

davidglassborow commented 10 years ago

Sorted, thanks