With these instructions, the bug can be reproduced. Contrary to the
commentary in ctypes.el, it does not help if you add (require 'ctypes)
to your Emacs init file, either.
The function ctypes-read-file is exposed as an autoload, and should
probably somehow (require 'cc-mode) directly or indirectly.
The simple straightforward fix for this specific bug is to add that to
the ctypes-read-file function and be done with it. But should the other
autoload functions have that, too? Or should perhaps ctypes.el simply
(require 'cc-mode) as a prerequisite for the whole module? (I imagine
it was a conscious design decision to not do that, but perhaps then that
issue should be revisited.)
If the original upstream author is responsive, perhaps these questions
should be brought up with him. (But PSG's comments further down in the
file indicate he is not reachable.)
For the record, here are repro steps showing how a new user could
realistically trigger this bug on a virgin install of Emacs and emacs-
goodies-el.
* M-x customize-group <ret> ctypes <ret>
Ctypes Install: toggle on and save for future sessions
Ctypes Write Types At Exit: enable and save for future sessions
* Visit a new file C-x C-f /tmp/ctypes.c and enter the following
contents:
typedef foo bar;
* M-x ctypes-buffer <ret> <ret>
* Quit Emacs; verify that ~/.ctypes was created when quitting Emacs
* Start a new Emacs instance
* M-: (setq debug-on-error t) ; maybe
* M-x ctypes-read-file <ret> ~/.ctypes <ret>
=> (void-varliabe c-font-lock-keywords-2)
** Changed in: emacs-goodies-el (Ubuntu)
Status: Incomplete => Confirmed
--
void variable with ctypes.el
https://bugs.launchpad.net/bugs/162954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
