On Jun 15, 2006, at 6:03 PM, Samuel Kleiner wrote: > On Jun 15, 2006, at 8:44 PM, Adrian Robert wrote: > > Thank you for your help, but I was not able to make it work- I > therefore found a newer csharp-mode: http://mfgames.com/linux/ > csharp-mode > this _also_ gives an error at initialization(below), but it at > least fontifies my buffer. > > File mode specification error: (void-variable compilation-error- > regexp-alist)
It sounds like looking into this directly might be the most effective way to go. >> 1) cc-mode in emacs-unicode-2 branch has not been updated to same >> code that is in trunk yet. > > Could be- I copied cc-mode from darwinports emacs.app 22.0.50 into > emacs.app site-lisp(and deleted the built-in). C-mode still works, > but when I started the old C# mode, I got another error: > File mode specification error: (error "Font-lock trying to use > keywords before setting them up") > >> 2) I have some modifications in Emacs.app cc-mode for improved >> handling Objective-C. I don't see how these could effect C#, but >> could be there is a bug somewhere. > > How would I detect this was the possibility? You could get the stock unicode-2 branch cc-mode by removing these files in the unpacked Emacs.app source tarball and running "cvs up" in that directory, then run 'byte-recompile-directory' in emacs on that directory, then build/install or copy these files to your existing installation. >> 3) Some of your own customization and/or site-lisp is loaded >> differently in Emacs.app vs. Carbon Emacs. To check this, try >> running both with the '-Q' (capital Q) option, and explicitly >> loading just the dependencies you need for C# mode. > > Tried it, ran only > (autoload 'csharp-mode "csharp-mode" > "Major mode for editing C# code." t) > (setq auto-mode-alist (cons '( "\\.cs\\'" . csharp-mode ) auto-mode- > alist )) > > and opened a .cs file, with the same results It sounds like you get different errors depending upon which cc-mode you use, so C# mode must be pretty sensitive to fine details and/or internals of cc-mode. It doesn't help that cc-mode seems to be evolving quite rapidly the past few months. For example, I observed some serious weirdness w/my Objective-C mode modifications for a few weeks, then they went away after some more CVS updates without me having changed anything. I think your best route is to see what you can do to temporarily manually fix the first error you report above (w/latest C# mode), and when the next Emacs.app release comes out you might be able to do without the fix. Adrian _______________________________________________ Emacs-app-dev- mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
