In several recent releases of Carbon Emacs, there's a literal ^L at
the bottom of the bundled cc-menus.el (Resources/lisp/progmodes).
This stops the file from working. Removing it brings back full
functionality for doing things like viewing an imenu of method names
in an Objective-C file.
I don't see it in the original Emacs source, so I think it may be a
bug in Carbon Emacs, specifically.
Am 02.10.2009 um 19:56 schrieb Geoffrey Grosenbach:
> In several recent releases of Carbon Emacs, there's a literal ^L at > the bottom of the bundled cc-menus.el (Resources/lisp/progmodes).
> This stops the file from working. Removing it brings back full > functionality for doing things like viewing an imenu of method names > in an Objective-C file.
That's not likely. Because no-one/nothing uses the Elisp file, only the byte-compiled version is used by Emacs. The source files added because GPL requires this.
On 2009/10/02, at 13:56, Geoffrey Grosenbach wrote:
> In several recent releases of Carbon Emacs, there's a literal ^L at > the bottom of the bundled cc-menus.el (Resources/lisp/progmodes).
> This stops the file from working. Removing it brings back full > functionality for doing things like viewing an imenu of method names > in an Objective-C file.
> I don't see it in the original Emacs source, so I think it may be a > bug in Carbon Emacs, specifically.
> In Emacs 22, you will see ^L in cc-menus.el > (e.g. /usr/share/emacs/22.1/lisp/progmodes/cc-menus.el.gz). > At present, Carbon Emacs is based on Emacs 22.
There's many of these in there. It's an old line feed. It's a stupid convention, especially because Emacs doesn't show it as line-feed.
Still, I don't see why this would break any functionality. Geoffrey, can you explain?
On Oct 2, 6:31 pm, David Reitter <david.reit...@gmail.com> wrote:
> Still, I don't see why this would break any functionality. Geoffrey,
> can you explain?
It sounds like I need to figure out the problem more specifically
before I can report a bug. An any rate, it does work for me if I
remove that line (could that force a recompilation of the file?).
So for the meantime I'll just do that on my installations of Carbon
Emacs. Maybe I'll figure out the reason why later.
Am 07.10.2009 um 22:50 schrieb Geoffrey Grosenbach:
> It sounds like I need to figure out the problem more specifically > before I can report a bug. An any rate, it does work for me if I > remove that line (could that force a recompilation of the file?).
Only if you rebuild the application from its sources.
And changing the EL file while the ELC is used cannot bring any change.
-- Greetings
Pete
Cabbage, n. A familiar kitchen-garden vegetable about as large and wise as a man's head.
On Thu, Oct 8, 2009 at 11:56 AM, Peter Dyballa <Peter_Dyba...@web.de> wrote: > And changing the EL file while the ELC is used cannot bring any change.
I'm sure that it is configured somewhere in my .emacs, but the copies of emacs that I have access to all prefer a newer *.el file to an older byte-compiled version.
If if there is a problem with a byte compiled file (corrupted in transfer, etc), merely touching the corresponding .el file will fix the problem.