X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Rugxulo Newsgroups: comp.os.msdos.djgpp Subject: Re: CC-Mode Syntax Highlight on Emacs Date: Mon, 22 Dec 2008 22:23:09 -0800 (PST) Organization: http://groups.google.com Lines: 25 Message-ID: <9c04f342-34a4-4524-9e09-3a628b8d389e@k8g2000yqn.googlegroups.com> References: NNTP-Posting-Host: 65.13.115.246 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: posting.google.com 1230013389 15843 127.0.0.1 (23 Dec 2008 06:23:09 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: Tue, 23 Dec 2008 06:23:09 +0000 (UTC) Complaints-To: groups-abuse AT google DOT com Injection-Info: k8g2000yqn.googlegroups.com; posting-host=65.13.115.246; posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5,gzip(gfe),gzip(gfe) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id mBN6U6Fm019442 Reply-To: djgpp AT delorie DOT com Hi, On Dec 22, 11:15 pm, IcEonFirE wrote: > > I am new Emacs' user; I have read the online documentation on DJGPP web site for the steps to enable the syntax highlight: I have added the three next lines to the default config in _EMACS.XMP file: > > (global-font-lock-mode t)(setq font-lock-maximum-decoration t)(global-highlight-changes-mode t) > There was no difference though: When I opened a C file,the text is black with gray background > > Any suggestions will be welcome. Thanks You shouldn't have to change anything, it should work out of the box. But I think your mistake is having no _EMACS file, which is the file that it expects. The _EMACS.XMPL file is just an "example" (== xmpl, get it?) written by Eli for you to "copy _emacs.xmpl _emacs" or rename or whatever. P.S. If you're really adventurous, try using CVS (via Cygwin, for example) to get Emacs 23.0 and test building it on your machine. (I assume here that you're using old 20.5, which doesn't support UTF-8, among other goodies.)