Mail Archives: djgpp/1996/03/26/11:25:48
On Tue, 26 Mar 1996, Michael Schuster wrote:
> Gruess Euch!
>
> I've read several times discussions about emacs in this group, and so
> I've downloaded it.
> I wanted to run the C/C++ hilighted mode (which was the reason for
> downloading EMACS 19.30 ) but I got two problems:
>
> 1. I've copied the _EXAMPLE -file to my emacs/bin directory to an
> _EMACS file, but there was no difference when envoking emacs.(I've
> changed the path to the bin-directory before). Also, if I write
> some nonsens in the _EMACS -File, emacs seems to be unimpressed
> and doesn't bring any error (... what a pitty no error...)
The place the _emacs is supposed to be installed is in your "~/home"
directory which under MS-DOG must be pointed manually by a environment
variable like SET HOME=C:\EMACS.
I've read a doc of earlier version of Emacs ported to MS-DOG (19.28 I
think which said the binary would look to the PARENT directory for the
_emacs file.
And last but not the least it is always possible to invoke Emacs with a
-l [some_dir]/_emacs and it will use the script you ask for (is the setup
we use here to cope with the variyng taste among users). A explanation of
it can be found in the info file about Emacs under "invoking Emacs".
> 2. The Font-lock-mode choosen manually with the [nonDOS-like] M-x
> -key is hilighting only some words like "include" but not "for" or
> "if)
>
For the font-lock-mode to work in full you must set a hook for it, in the
example _EXAMPLE you cited there is some hints.
If you (or anybody) needing more details, we can post a more thorough
procedure; but it can be found also in the info file under "customizing
Emacs".
> I know that this is perhaps not quite the right group for this mail, but I don't
> know where to mail else.
>
> Michi
>
According to Eli, at least for the DJGPP ported version, it is OK to post
here questions about Emacs!
Cheers,
- Raw text -