ANNOUNCE: DJGPP port of GNU Emacs 23.3 uploaded
Eli Zaretskii
of the latest official release 23.3 of GNU Emacs is available from the
DJGPP site near you:
ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/em2303b.zip
ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/em2303s.zip
(and soon from all the mirrors).
The binaries were built on Windows XP. I no longer have access to a
plain DOS machine. I would be interested to know whether this version
builds and runs on plain DOS; please report any positive or negative
experiences to dj...@delorie.com.
As my main development platform is no longer DJGPP, I could only test
this port superficially. But if you report any problems (preferably
with a patch to fix them), I will try to diagnose and/or fix them in
the upstream repository.
Send any suggestions and bug reports concerning the DJGPP port to
comp.os.msdos.djgpp or <dj...@delorie.com>.
Enjoy.
Rugxulo
On Apr 25, 9:45 am, Eli Zaretskii <e...@gnu.org> wrote:
>
> After a long, long, LONG, time without regular updates, a DJGPP port
> of the latest official release 23.3 of GNU Emacs is available from the
> DJGPP site near you:
All together now: "For he's a jolly good fellow, for he's a jolly
good fellow, ...". :-))
Wiktor S.
Haven't tried to build it, because my DOS machine is already low on disk
space.
--
Azarien
Eli Zaretskii
> Date: Fri, 29 Apr 2011 18:42:05 +0200
> Bytes: 1337
>
> I can confirm it runs on MS-DOS 6.22.
Thanks for the feedback. This is very good news.
Rugxulo
On Apr 29, 1:21 pm, Eli Zaretskii <e...@gnu.org> wrote:
> > From: "Wiktor S." <wswikto...@Mpoczta.fm>
> > Date: Fri, 29 Apr 2011 18:42:05 +0200
> > Bytes: 1337
>
> > I can confirm it runs on MS-DOS 6.22.
>
> Thanks for the feedback. This is very good news.
I installed it in C:\EMACS under DOSEMU x86-64 (Fedora 14) on my jump
drive. It (mostly) works there. I need to double-check the INSTALL
file or such to make sure I didn't do it wrong (it's been a while
since I installed Emacs binary-only). I know you prefer (or
recommend?) installing inside the DJGPP tree, but what if there is no
DJGPP tree? I know I know, silly idea, but still .... ;-) I sadly
can't reliably test many other places since some of my other machines
are disconnected.
Eli Zaretskii
> Date: Mon, 9 May 2011 13:35:20 -0700 (PDT)
>
> I installed it in C:\EMACS under DOSEMU x86-64 (Fedora 14) on my jump
> drive. It (mostly) works there.
"Mostly" meaning what?
> I know you prefer (or
> recommend?) installing inside the DJGPP tree, but what if there is no
> DJGPP tree?
Then you will need to copy the djgpp.env file to the grand-parent
directory of the top-level Emacs directory, the one above the
`gnu/emacs' directory, and you will need to point the DJGPP
environment variable to that djgpp.env file. That's all, I think,
except that if you don't have a `bin' directory with ports of GNU
software, quite a few Emacs features won't work because they need
those external programs.
Thanks.
Rugxulo
On May 10, 2:22 am, Eli Zaretskii <e...@gnu.org> wrote:
> > From: Rugxulo <rugx...@gmail.com>
> > Date: Mon, 9 May 2011 13:35:20 -0700 (PDT)
>
> > I installed it in C:\EMACS under DOSEMU x86-64 (Fedora 14) on my jump
> > drive. It (mostly) works there.
>
> "Mostly" meaning what?
In other words, I don't know if this is due to my (raw) install or
not, but while in Dired, pressing "e" for edit didn't work for certain
files. Most worked, but one or two (e.g. "blah.sh") seemed to just
abort unexpectedly and close the console / terminal. But since this is
DOSEMU, it could just be a bug (or PEBKAC). ;-) I'd have to try
again later. (Frustratingly, my wifi doesn't work there [yet], else
I'd probably use it more often.)
> > I know you prefer (or
> > recommend?) installing inside the DJGPP tree, but what if there is no
> > DJGPP tree?
>
> Then you will need to copy the djgpp.env file to the grand-parent
> directory of the top-level Emacs directory, the one above the
> `gnu/emacs' directory, and you will need to point the DJGPP
> environment variable to that djgpp.env file. That's all, I think,
> except that if you don't have a `bin' directory with ports of GNU
> software, quite a few Emacs features won't work because they need
> those external programs.
The "quite a few" isn't a direct problem for me. Let's face it, Emacs
is pretty huge in functionality already, so I'd be surprised if I ever
used even half of it. But yeah, sure, some of it won't work without
other stuff (Ediff needs Diff, VC needs RCS or whatever ... not that I
ever used those modes [yet], honestly).
P.S. Do you still read news://gnu.emacs.help or http://www.emacswiki.org
?
Rugxulo
> > > I know you prefer (or
> > > recommend?) installing inside the DJGPP tree, but what if there is no
> > > DJGPP tree?
>
> > Then you will need to copy the djgpp.env file to the grand-parent
> > directory of the top-level Emacs directory, the one above the
> > `gnu/emacs' directory, and you will need to point the DJGPP
> > environment variable to that djgpp.env file. That's all, I think,
> > except that if you don't have a `bin' directory with ports of GNU
> > software, quite a few Emacs features won't work because they need
> > those external programs.
I double-checked the emacs23.README file, it doesn't mention DJGPP.ENV
at all (but does say put `gnu/emacs/bin' in your PATH). I know you
probably just briefly edited it from the old version, but IMHO, it
should say a few extra things:
* Vista/7 have DPMI bugs, registry hack may help (but may need
recompile with "system malloc") [I know this is probably in INSTALL
already]
* NT 4 LFNs probably work with NTLFN driver / TSR combo [but NT 4 is
quite rare these days]
* not every programming language *.el for font lock (syntax
highlighting) is included by default, e.g. Oberon, Rexx, etc. [why?
GNU policy??]
* htmlize (or whatever it's called) is now included [forgot to test
it]
* no more MULE by default but real Unicode!
* man + less + gawk + sed isn't needed, just use "woman" (w/o man)
Bugs:
* (old, not important) if you have something like '"' (double quote
inside single), it will screw up syntax highlighting for the rest of
the file, which is somewhat annoying. ;-)
* not sure, but I don't think it highlighted *.mod (Modula-2) by
default at all (unlike others), I may have had to do it manually
[incidentally my attempts a few months ago to compile GM2/GCC 4.1.2
via DJGPP failed]
Yeah, I know, there are tons of little details like that (and I forgot
to check if you ever added cp853 support, heh, but I doubt you did, no
biggie anyways, nobody cares, and me only barely).
P.S. gomoku still beats my ass, and while zone works, it seems to hang
if done on finished gomoku buffer (oops). And BTW, having yow with
only a single sentence is pointless, why don't the GNU peeps just
write their own copylefted taglines?? :-P
Long story short: huge thanks for your efforts! (I need to announce
this for the FreeDOS peeps.) >:D<
Eli Zaretskii
Rugxulo
Note that this isn't hugely important (obviously), esp. since I
know you're always busy. Feel free to ignore, but I'm commenting just
in case it matters ....
> On May 10, 2:22 am, Eli Zaretskii <e...@gnu.org> wrote:
>
> > > From: Rugxulo <rugx...@gmail.com>
> > > Date: Mon, 9 May 2011 13:35:20 -0700 (PDT)
>
> > > I installed it in C:\EMACS under DOSEMU x86-64 (Fedora 14) on my jump
> > > drive. It (mostly) works there.
>
> > "Mostly" meaning what?
>
> In other words, I don't know if this is due to my (raw) install or
> not, but while in Dired, pressing "e" for edit didn't work for certain
> files. Most worked, but one or two (e.g. "blah.sh") seemed to just
> abort unexpectedly and close the console / terminal. But since this is
> DOSEMU, it could just be a bug (or PEBKAC). ;-) I'd have to try
> again later.
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). And
*.mod still isn't recognized by default for font-lock. IIRC, Emacs
needs (at compile time?) to know in advance what *.el font lock files
are available, hence people always seem to have to manually do "add
alist" (or whatever, I forget) in their .emacs / _emacs file in order
for it to work automagically. (Most others, e.g. Pascal, work fine by
default.) Oh, and '\' is treated as a C escape, so that also messes up
font lock for the rest of the file, heh, oh well.
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.)
Eli Zaretskii
> 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.
Rugxulo
On May 11, 11:58 pm, Eli Zaretskii <e...@gnu.org> wrote:
> > From: Rugxulo <rugx...@gmail.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?
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? 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".
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. 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
This is what I always see people doing, but it always seems kludgy to
me.
> . 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.)
Eli Zaretskii
> Date: Thu, 12 May 2011 05:48:48 -0700 (PDT)
>
> > 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.
Okay. If you have a few moments to spare, please try this:
. Try just loading sh-script (M-x load-library RET sh-script RET)
and see if that alone crashes DOSEMU.
. Disable font-lock globally (M-x global-font-lock-mode RET) before
typing `e' on the .sh file, and see if DOSEMU still crashes.
. If both of the two previous items didn't crash, enable font-lock
and try bisecting that .sh file until you find which part causes
the crash. (I assume that font-lock in other modes doesn't cause
a crash, so font-lock by itself is not the reason.)
Rugxulo
On May 12, 12:27 pm, Eli Zaretskii <e...@gnu.org> wrote:
> > From: Rugxulo <rugx...@gmail.com>
> > Date: Thu, 12 May 2011 05:48:48 -0700 (PDT)
>
> Okay. If you have a few moments to spare, please try this:
>
> . Try just loading sh-script (M-x load-library RET sh-script RET)
> and see if that alone crashes DOSEMU.
No, apparently it does not.
> . Disable font-lock globally (M-x global-font-lock-mode RET) before
> typing `e' on the .sh file, and see if DOSEMU still crashes.
I don't think that changed anything, but honestly I forget (so much to
remember).
> . If both of the two previous items didn't crash, enable font-lock
> and try bisecting that .sh file until you find which part causes
> the crash. (I assume that font-lock in other modes doesn't cause
> a crash, so font-lock by itself is not the reason.)
I don't think it's my (admittedly noob-ish) .sh files. "emacs blah.sh"
works fine, font-lock works, and sh-script mode is loaded. It's just
somehow through Dired it doesn't work. Similarly with auto-compression-
mode on a .ZIP (crash). I'm fairly certain it's just a quirk (no)
thanks to AMD64 / DOSEMU. I really need to try on my 32-bit Linux
machine too. (Yeah, probably should've avoided 64-bit, but long story
short, I didn't, I took the easy way out. Also should probably get my
old laptop repaired, but that's more to do. And get wifi working under
Fedora. And a billion other things. Ugh.)
Rugxulo
On May 14, 3:42 pm, Rugxulo <rugx...@gmail.com> wrote:
>
> I don't think it's my (admittedly noob-ish) .sh files. "emacs blah.sh"
> works fine, font-lock works, and sh-script mode is loaded. It's just
> somehow through Dired it doesn't work. Similarly with auto-compression-
> mode on a .ZIP (crash). I'm fairly certain it's just a quirk (no)
> thanks to AMD64 / DOSEMU. I really need to try on my 32-bit Linux
> machine too.
Hours and hours and hours of testing later ... yes, DOSEMU (32-bit)
works fine. sh-script-mode works fine via Dired ('v') via Unzip. And I
discovered that modula-2-mode is the one with the '\' bug, yet for the
exact same thing, pascal-mode works fine (go figure). More minor
testing will follow eventually, but I'll try not to bug you, Eli, at
all if possible (only big stuff, not silly things like syntax
highlighting).
I probably shouldn't have even wasted your time with such an oddball
testing environment (DOSEMU, esp. x86-64), but I figured it was worth
(barely) testing. My bad. :-/
<rant>
Not to rag on Fedora (sorry, DJ), but I couldn't get my wifi to work
initially. I (very naively) thought a "full upgrade" (400 MB) would
get me a newer ("better"??) kernel, but that literally took all night.
And it hosed the jump drive's install, heheh. Then I grabbed F15 beta
to test. And then I could get wifi to work (once I found the correct
firmware, *shakes fist*) with goofy GNOME 3. When F15 final came out
two days ago, I upgraded, and I finally decided to stop being crazy
and just use 32-bit DOSEMU (V86 mode, ftw!). However, F15 doesn't save
persistent changes! I ended up downloading at least twice, reimaging
several times, even tried again after they (finally) updated the
liveUSB tool. And it still doesn't save changes. So back to F14 (i686)
I went. At least now (!) wifi and DOSEMU work okay and save changes
for me, sheesh.
Of course, you'll have to use rpmfind.net to grab "non-free" DOSEMU as
Fedora is insanely strict (same as Debian) because the FreeDOS kernel
(compact model) needs OpenWatcom to *rebuild!!!!* (OSI approved but
"not good enough"). DOSBox is not even close to suitable, "only meant
for games"! Once you get that installed and kill the initial crash /
bug (can't find shell but it figures it out later anyways), you also
have to do two things (or something similar, this is from memory):
"su -c 'sysctl -w vm.mmap_min_addr=0" and "su -c 'sesetbool -P
mmap_low_allowed 1'". So yeah, works great once you get all that
sorted out! (But no, I haven't done any heavy DJGPP testing yet. In
very limited prior experience a few months ago, I had lots of problems
with DJGPP's "./configure && make", which I think actually hung DOSEMU
a few times at the config.status generation stage, ugh. Dunno why.)
</rant>
> (Yeah, probably should've avoided 64-bit, but long story
> short, I didn't, I took the easy way out. Also should probably get my
> old laptop repaired, but that's more to do. And get wifi working under
> Fedora. And a billion other things. Ugh.)
Old old P166's floppy drive broke (again). One P4 (which had XP until
that hosed itself, HD problems?) has PuppyLinux + DOSEMU via USB boot,
but I don't use it as much (kinda a kludgy machine). Other P4 has XP
but is disconnected (need a KVM, "yet another" thing to do!!). And (I
hate to say) I've been somewhat more preoccupied than usual. So my
options for running DJGPP's Emacs weren't perfect.
I guess I (have to) give up on the (semi-useful) Windows + DJGPP combo
unless I can resurrect that old P4 (either buy a KVM or find bro's old
one, but none of that's urgent by any means). I just wasn't too
careful (and honestly have no "need") re: 32-bit vs. 64-bit. I just
poke around, just a silly hobbyist. For laughs I thought "trying"
DOSEMU x86-64 would be interesting, but long story short, some stuff
works, most doesn't. So it's not perfect by any means. And VirtualBox
would be nice but needs a decent FreeDOS setup / image, which I don't
have [yet] (and nobody else seems to care to make one). FD 1.0 is too
big and too old, IMHO. But perhaps I should've tried that anyways.
(Unfortunately, I'm not sure any of it is ideal for building DJGPP
stuff, neither pure FreeDOS [even w/ DOSLFN] nor DOSEMU nor WinXP. But
at least the latter mostly works. Too bad that's the worst choice
nowadays.)
So there. Hopefully that explains some stuff or helps somebody
somewhere (barely, though I doubt it). :-P
Eli Zaretskii
> Date: Thu, 26 May 2011 15:23:25 -0700 (PDT)
>
> Hours and hours and hours of testing later ... yes, DOSEMU (32-bit)
> works fine.
OK, that's good to know.
> More minor testing will follow eventually, but I'll try not to bug
> you, Eli, at all if possible (only big stuff, not silly things like
> syntax highlighting).
No sweat. I actually prefer that you tell about every problem you
find, both for the record, and because you can never know which one of
them is a tip of an iceberg. And I can assure you I will not spend
too much time on purely DJGPP problems in Emacs, as most of my scarce
resources are taken anyway (adding bidirectional editing support to
Emacs).