Re: c-subword-mode

[Nick Roberts <nickrob@snap.net.nz>]

 >     Sometimes I get error messages saying that c-subword-mode is a void
 >     variable.  c-subword-mode seems to be a function, so the patch below
 >     might be a fix.
 > 
 > That patch seems wrong to me.  If c-subword-mode is defined as a function 
 > and not as a variable, your patch will CAUSE such an error rather than
 > prevent it.

Yes it probably is wrong, but I don't see the point of the test if
c-subword-mode is a function.

 > Can you provide a Lisp-level backtrace from some occasion where you
 > get that error?

If I load a C file, I get:

Debugger entered--Lisp error: (void-variable c-subword-mode)
  c-update-modeline()
  c-basic-common-init(c-mode ((java-mode . "java") (awk-mode . "awk") (other . "gnu")))
  c-common-init(c-mode)
  c-mode()
  set-auto-mode-0(c-mode nil)
  set-auto-mode()
  normal-mode(t)
  after-find-file(nil t)
  find-file-noselect-1(#<buffer myprog.c> "~/myprog.c" nil nil "~/myprog.c" (458851 773))
  find-file-noselect("~/myprog.c" nil nil t)
  find-file("~/myprog.c" t)
  call-interactively(find-file)

It's probably due to my build.  If I load cc-mode first, I don't get the error.


-- 
Nick                                           http://www.inet.net.nz/~nickrob


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642