Skip to content

c-mode conflict with auto-complete [yas] Error in condition evaluation: Symbol's function definition is void: nil #347

Closed
toolchainX opened this Issue Dec 14, 2012 · 3 comments

2 participants

@toolchainX

I come across the problem when I open a new c source file such as test.c. In my c-mode the auto-complete-mode and the yas-minor-mode is enabled by default.
every time I write a comment start with // or /* (which both are the comment notation in C) at the very top line(i.e. the first line) of the test.c file, the minor buffer prompt [yas] Error in condition evaluation: Symbol's function definition is void: nil. there is no other side effects just the Error Prompt. with the auto-complete-mode disabled the problem is gone, I think there maybe something conflict with the two plugins
I reproduced the problem with the minimal code in dot-emacs, here is the code:

(add-to-list 'load-path
         "~/.emacs.d/plugins/yasnippet")
(add-to-list 'load-path "~/.emacs.d/plugins/auto-complete")
(require 'auto-complete)
(require 'auto-complete-config)
(add-to-list 'ac-dictionary-directories "~/.emacs.d/plugins/auto-complete//ac-dict")
(require 'auto-complete-config)
(ac-config-default)
(require 'yasnippet)
(yas-global-mode t)

my emacs version is GNU Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-29 on MARVIN
my auto-complete version(1.4.0) is got from the github in 2012-11-13 18:51
my yasnippet version(0.8.0) is got from the github in 2012-11-13 16:44

@capitaomorte
Owner

Nice error report. I'll have a look soon.

@capitaomorte
Owner

Thanks for the report. However to sucessfully (require 'auto-complete) one must do

cd ./Source/Emacs/auto-complete
git submodule init
git submodule update
cd ../../../
emacs -Q -L ./Source/Emacs/yasnippet\
         -L ./Source/Emacs/auto-complete\
         -L ./Source/Emacs/auto-complete/lib/popup\
         -L ./Source/Emacs/auto-complete/lib/fuzzy\

Also it must be

 (add-to-list 'ac-dictionary-directories "~/Source/Emacs/auto-complete/dict)
@toolchainX

problem solved thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.