Mail Archives: djgpp/2002/02/13/06:19:26
On 13 Feb 2002, Thomas Mueller wrote:
> I guess I could, when ready, download Emacs source and build for DOS, Linux and
> NetBSD from the same source?
Yes, but there's a gotcha. The DJGPP version is built in-place, in the
same directory tree where the sources are, and then used from that tree
(you can remove the src directory and a few others, once you've built the
program). So if you want to use a single source tree for building all
those versions, first build the Unix versions from two different build
directories, and only then build the DJGPP version.
Alternatively, you can make a copy of the source tree, at the expence of
more disk space.
> >> If you read all your email in DOS Emacs, what do you use to send and receive
> >> email?
>
> >Emacs, of course ;-)
>
> I was wondering how Emacs Internet capabilities would work with DOS packet
> drivers such as DOSPPPD (EPPPD) and LSPPP.
As you've seen, my solution doesn't need any DOS packet drivers, since
Blat is a Win32 console application. However, a similar solution should
work with DOS drivers, assuming you can find a command-line mailer that
works on MS-DOS.
On other platforms, Emacs has a built-in network support (although the
default configuration on those systems doesn't use that support for
email), but those network capabilities aren't supported in the DJGPP
port, because of lack of time and interest in implementing it, and
because there's no satisfactory solution (IMHO) for DJGPP networking
that works on most or all supported platforms.
> Besides feedmail and Blat, there is GNUS, and I notice some others in message
> header lines.
Gnus needs either built-in networking or clients for several protocols
(such as NNTP) to run.
> I tried viewing the Korean spams in Emacs with --unibyte switch, just to see
> what would show. Naturally I didn't expect to see actual Korean characters.
> I also viewed the HELLO file in Emacs with and without --unibyte, and also in
> Tiny Editor (DOS-based and also a 16-bit OS/2 version). Emacs with --unibyte
> showed ^[ in some places, where Tiny Editor showed left-arrow, indicating
> ASCII 27, suggesting an ANSI escape sequence.
Try without --unibyte. You will see empty boxes, since Emacs cannot
display those characters. However, if you type "C-u C-x =" with the
cursor on one of these boxes, Emacs will tell you that it's Korean
character, and will show its encoding in hex. (It does indeed include
escape sequences). Also, if you install the necessary font files (see
the file emacs.README on SimTel.NET), you will be able to print the
entire HELLO file with all the scripts, including Korean, and see all the
characters in all their glory.
Admittedly, this is not very practical support for Korean, but I don't
see how can Emacs do better without the fonts built into DOS. I did try
running the DJGPP port in Japan once, and it did display Japanese
characters correctly on a Japanese version of Windows 95. So I know it
does work.
> Since I might want to view the same file in another environment or
> configuration, I don't want Emacs to permanently convert characters in strange
> character sets to ASCII 127 and save that way if I edit the file.
In v20.x, this requires constant attention. Emacs 21 doesn't convert
unknown characters into ASCII 127, so it's safer.
- Raw text -