From: Eric M. Ludlam <ericludlam@gm...> - 2011-06-25 01:48:35
I don't know how the latest Emacs built-in cedet works, but the
In the external CEDET the which-func feature is handled by advice around
the function 'which-function' which you can disable with ad-disable-advice.
If that advice was bound into which-function during the merge, then
perhaps it could just be fixed by just fixing the override, such as:
js-mode () ;; use the correct mode name
"Ignore requests for local variable declarations from the current
I'm not sure why that error doesn't show up in more places for more
languages that fail to create the above override.
On 06/23/2011 08:01 AM, Oleksandr Gavenko wrote:
> How disable semantic for specific mode?
> I use only built-in GNU Emacs CEDET.
> This articles provide solution:
> but for me this instructions seems outdated or irrelevant for GNU Emacs
> built-in CEDET as none of *-mode-hook contain
> 'semantic-default-*-setup' (but I do not comment and recompile
> semantic files).
> I enable semantic by
> (semantic-mode 1)
> Search for'disable' in (info"semantic") take no result.
> I want to disable Semantic for js-mode because of bug:
> 'which-func-mode' can not find function when'semantic' enabled.
> "wisent-parse-stream: #<buffer my.js> - Invalid start symbol
> "(global-semantic-idle-summary-mode 1)"
> Also I think semantic for JS less useful as JS not strong typed lang
> and dabbrev completion work much fine.
> Simplify data backup and recovery for your virtual environment with vRanger.
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today.
> cedet-semantic mailing list