Mail Archives: djgpp/2011/05/12/09:00:17
Hi,
On May 11, 11:58=A0pm, Eli Zaretskii <e DOT DOT DOT AT gnu DOT org> wrote:
> > From: Rugxulo <rugx DOT DOT DOT 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. =A0Does every .sh file cause a
> crash? =A0What other files are "not okay", and in what ways?
Dunno, would have to test more. (*.ob2? Can't remember offhand.)
Remember, this is DOSEMU x86-64, so it's not as good as the
traditional 32-bit one. So more than likely it's their "bug" (or lack
of support).
Honestly, I don't care for 64-bit (and don't "need" it personally, but
it is fast becoming ubiquitous), but for whatever reason I thought I
should test DOSEMU there for a while, for curiosity, to see how
compatible it is.
Perhaps I shouldn't bug you with comments when tested in such an
"unstable" environment. Well, I have 32-bit DOSEMU on my other
computer, so I guess I should install DJGPP Emacs there too, for
reference. (Or get/make another jump drive.)
> Can you post the traceback, even if it's just numerical addresses?
No because there is no traceback. I didn't mean it "crashes", it may
not at all, but it definitely closes the whole "DOS in a box" terminal
window, which means something somewhere is aborting it. It may just be
some 16-bit code incompatibility (most likely).
> > 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? =A0I see "Fundamental", which makes sense because .mod is not in
> auto-mode-alist. =A0So this is a missing feature in Emacs, not a
> DJGPP-specific bug. =A0Feel free to ask for an enhancement by typing
> "M-x report-emacs-bug RET".
Well, it's not important, and it's an easy fix (just turn it on!). I
just wanted to mention it since it seemed out of place (Pascal works
by default, Modula-2 doesn't). Seems too trivial to report it.
> > IIRC, Emacs needs (at compile time?) to know in advance what *.el
> > font lock files are available
>
> That's not true. =A0If you have some optional mode that is not part of
> Emacs, you need to set it up:
>
> =A0 . put it somewhere where Emacs will find it (the recommended place
> =A0 =A0 is the site-lisp subdirectory)
>
> =A0 . add an autoload command for it in your _emacs
This is what I always see people doing, but it always seems kludgy to
me.
> =A0 . add an appropriate association to auto-mode-alist.
This is what I meant. I guess I was naive to think it would
"magically" find any font lock *.el files and magically know when to
highlight. In TDE, the *.shl (syntax highlight file) has file name
extensions listed in it for each language, so it always knows which
are valid. But perhaps somebody somewhere (somewhat doubtful) thought
*.mod was "too generic" (Amiga sound module?).
> > 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?
Modula-2, I think, but possibly others too. This is more than likely
just a built-in limitation of the way Emacs handles font lock. Or
perhaps it's just a corner case that nobody worries about. Some
languages do indeed let you use \ as an escape, but others don't, so
it's only incorrect some of the time.
> > 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.
Heh, yes, I know. I could also (re)grab enwik8 and copy it 5x. Hmmm, I
forgot Project Gutenberg had some interesting documents that would fit
the bill. (I just grabbed one that was 5.9 MB, yow, cabbage-brained!)
(Hope this wasn't too much of wasting your time.)
- Raw text -