Texinfo mode completion error

Finally trying to get some work done in texinfo mode, I came across this. Looks like it was trying to complete an @declaration…?

Debugger entered--Lisp error: (wrong-number-of-arguments #[(context) "\306\307\"@\310\306\311\"\235\203!	\312\313O\314
\"\315\316\"*\202;\317\306\311\"\235\203:\320\321!\210\322	!\315\323
\")\202;\313)\207" [context prefix cmd semantic-texi-command-completion-list lst word-list eieio-oref :prefix function :prefixclass 1 nil all-completions mapcar #[(f) "\304P\305\306\211
\307	!\306\211\257+\207" [f attributes class name "@" function nil semantic-tag-make-plist] 6] word require ispell ispell-lookup-words #[(f) "\304\305\211
\306	!\305\211\257+\207" [f attributes class name word nil semantic-tag-make-plist] 6]] 4 "List smart completions at point.
Since texinfo is not a programming language the default version is not
useful.  Instead, look at the current symbol.  If it is a command
do primitive texinfo built ins.  If not, use ispell to lookup words
that start with that symbol.

Override semantic-analyze-possible-completions in `texinfo-mode' buffers."] 2)
  semantic-analyze-possible-completions-texinfo-mode([object semantic-analyze-context "Context-for-texinfo" (24755 . 24765) ("compilaton") (word) nil nil #<buffer ede.texi> unbound] nil)
  semantic-analyze-possible-completions([object semantic-analyze-context "Context-for-texinfo" (24755 . 24765) ("compilaton") (word) nil nil #<buffer ede.texi> unbound])
  semantic-analyze-completion-at-point-function()
  completion--capf-wrapper(semantic-analyze-completion-at-point-function optimist)
  run-hook-wrapped(completion--capf-wrapper semantic-analyze-completion-at-point-function optimist)
  company--capf-data-real()
  company--capf-data()
  company-capf(prefix)
  #[0 "\n\203	\nC\202\n\211\205\220\211@\300
9\204\306!\203<
9\2036
\307N\310=\2046
\307N?\205@\311!\205@
\312!\202@\313\312\"\240\210\300\242\203\211\314\300\242!\203\203\315\300\242!\211\301\316\f!\240\210\301\242:\204l
\203\203\317\320!\210\202\203
\203t\300\242\321\301\242!\210\322\323\324 \"\210\325\326!\210\327\330\301\242\"\210
A\266\202\202\n\207" [(nil) (nil) company-backend company-backends company-prefix company--manual-action functionp company-init t company-init-backend prefix company--multi-backend-adapter company--good-prefix-p company--prefix-str company-calculate-candidates message "No completion found" company-update-candidates run-hook-with-args company-completion-started-hook company-explicit-action-p company-call-frontends show throw --cl-block-nil-- company--manual-prefix] 6 "\n\n(fn)"]()
  funcall(#[0 "\n\203	\nC\202\n\211\205\220\211@\300
9\204\306!\203<
9\2036
\307N\310=\2046
\307N?\205@\311!\205@
\312!\202@\313\312\"\240\210\300\242\203\211\314\300\242!\203\203\315\300\242!\211\301\316\f!\240\210\301\242:\204l
\203\203\317\320!\210\202\203
\203t\300\242\321\301\242!\210\322\323\324 \"\210\325\326!\210\327\330\301\242\"\210
A\266\202\202\n\207" [(nil) (nil) company-backend company-backends company-prefix company--manual-action functionp company-init t company-init-backend prefix company--multi-backend-adapter company--good-prefix-p company--prefix-str company-calculate-candidates message "No completion found" company-update-candidates run-hook-with-args company-completion-started-hook company-explicit-action-p company-call-frontends show throw --cl-block-nil-- company--manual-prefix] 6 "\n\n(fn)"])
  company--begin-new()
  company--perform()
  #[0 "\301 \210\207" [company-candidates company--perform] 1 "\n\n(fn)"]()
  funcall(#[0 "\301 \210\207" [company-candidates company--perform] 1 "\n\n(fn)"])
  company-auto-begin()
  company-idle-begin(#<buffer ede.texi> #<window 3 on *Backtrace*> 3856 24755)
  apply(company-idle-begin (#<buffer ede.texi> #<window 3 on *Backtrace*> 3856 24755))
  byte-code("r\301\302H\303H\"\210)\301\207" [timer apply 5 6] 4)
  timer-event-handler([t 21776 47559 674920 nil company-idle-begin (#<buffer ede.texi> #<window 3 on *Backtrace*> 3856 24755) nil 0])


Has there been any thought about actually using a bug tracker for CEDET?


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Cedet-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cedet-devel