Mail Archives: djgpp/2011/05/12/01:19:15
> From: Rugxulo <rugxulo AT gmail DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Wed, 11 May 2011 12:12:37 -0700 (PDT)
>
> Okay, tried again (DOSEMU), added C:\EMACS\GNU\EMACS\BIN to %PATH%
> just in case (didn't help). Still crashed when typing 'e' (edit) under
> Dired (C-x d) on blah.sh file (though most other files are okay).
It doesn't crash for me on Windows XP. Does every .sh file cause a
crash? What other files are "not okay", and in what ways?
Can you post the traceback, even if it's just numerical addresses?
> And *.mod still isn't recognized by default for font-lock.
When you visit a *.mod file, do you see some special mode being turned
on? I see "Fundamental", which makes sense because .mod is not in
auto-mode-alist. So this is a missing feature in Emacs, not a
DJGPP-specific bug. Feel free to ask for an enhancement by typing
"M-x report-emacs-bug RET".
> IIRC, Emacs needs (at compile time?) to know in advance what *.el
> font lock files are available
That's not true. If you have some optional mode that is not part of
Emacs, you need to set it up:
. put it somewhere where Emacs will find it (the recommended place
is the site-lisp subdirectory)
. add an autoload command for it in your _emacs
. add an appropriate association to auto-mode-alist.
> Oh, and '\' is treated as a C escape, so that also messes up
> font lock for the rest of the file, heh, oh well.
In what mode?
> Other than these (very) minor quibbles, it works! So I'm not
> complaining. (Though I don't have any 512 MB files to test, heh.)
You can easily create it with a simple Awk script which writes lines
of fixed length.
- Raw text -