home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 5 Edit
/
05-Edit.zip
/
me34exe.zip
/
readme.os2
< prev
Wrap
Text File
|
1995-01-21
|
6KB
|
138 lines
-*-text-*-
The is the README for an OS/2 port of ME3. It contains binaries and
patches for
ME3 (the Mutt Editor v3.4)
MC2 (the Mutt Compiler v2.6)
and the source for
Mutt extensions to ME3 (v1.4)
See the README file for more information.
See the file me34src.zip (uploaded to hobbes.nmsu.edu along with these
binaries) for the sources, and additional documentation.
To exit any emacs-style editor, press Ctrl-X Ctrl-C.
This port was done using the EMX version of the GNU C compiler. You will
have to change some of the code if you want to compile with another
compiler (I've given some hints below). The supplied makefiles are
set up to build three configurations:
emx-mt builds an OS/2-only executable. C library functions are
taken from emxlibc.dll, which makes the executable a little
smaller. emx.dll and emxlibc.dll are both required to run.
Get them from emxrt.zip, which should be somewhere at hobbes.
The editor and macro-compiler are in the bin directory of
this distribution.
emx-st builds an OS/2-only executable. The executable is about 30K
bigger than the emx-mt one, but emx and emxlibc aren't
required, so this will take less space if you don't have the
.dlls already. The editor and macro compiler are in the
bin/static directory of this distribution.
emx-dos builds an executable which can run under both DOS and OS/2.
DOS requires emx.exe, and OS/2 requires emx.dll. In a DPMI
environment (eg, Windows or OS/2 DOS box), use rsx.exe
instead of emx.exe for the DOS extender. The video in this
version is a bit slower than the OS/2-only versions (with
RSX, the video in this version is a bit of a joke -- get
rsxwin and see if that's any better). The editor and macro
compiler are in the dos directory of this distribution.
The original OS/2 port of ME was done by John Burnell. This port was done
by Patrick TJ McPhee, ptjm@io.org (Toronto Canada)
ME expects to find .mco (compiled macros) files in a directory called
c:/me3. You can set an environment variable to change its idea of where
to look:
ME3=c:/tools/me3;c:/projects/me3;t:/editors/macros/me3
Under DOS, with emx.exe, you need to set another environment variable:
EMXOPT=-acm
I tried binding it into the executable, but that makes rsx.exe blow up.
Put emx.exe (or rsx.exe) somewhere in your path. ME will load it
automatically. You need to use rsx.exe to run ME under Windows. RSX
doesn't seem to use direct-memory IO, and the screen updates are pretty
poor. I use a 16 bit version of ME when I'm working under Windows, and
load up the 32 bit version when I want to look at several large files
all at once.
I'd like to publicly express my gratitude to C Durland for the work he's
done making ME such a versatile and pleasant-to-use tool. I should add
that this port wouldn't be possible without the work of E Mattes on the
EMX environment.
How to Compile ME for OS/2
--- -- ------- -- --- ----
Compiling
---------
The OS/2 port is provided as a set of files which are not in the
original distribution, and a set of patches to files from the original
distribution. After unzipping the original sources (me34src.zip) and
the port sources, you need to apply the patches. Get Larry Wall's patch
program, and use it. As I recall, with version 1.2, all you had to do
was type
patch patches.os2
and all the patches would be applied. With the current version, it
seems you have to type
patch me/config.h patches.os2
and all the patches will be applied.
Once you've patched the sources, you need to copy emx1io.c, emx2io.c,
and os2kmap.c from me/misc to me. After that, you should be able to
type, eg,
make -f makefile.emx emx-mt
to build the emxlibc.dll version of editor. Unfortunately, none of the
makes that I've tried can change directories, so I've provided batch
files to build the editor in case your make can't cd. The command is
buildmt
to build the emx-mt version. If you don't use dmake, you'll have to
change the batch files to start your make program.
You might want to change me/config.h. In particular, if you don't want
to put your .mco files in c:/me3, change the definition of
DEFAULT_MUTT_SEARCH_PATH.
If you don't use the EMX compiler, this port probably won't help you too
much. emx1io.c is just John Burnell's os2io.c, with some changes to
reflect changes in ME, and some functions that EMX doesn't support
dropped. Either emx1io or os2io is a reasonable starting point for
another compiler. emx2io.c uses a video library which is peculiar to
EMX, so don't bother even looking at it.
I use a few function calls which are peculiar to EMX. _fnlwr takes a
filename as its argument. It determines whether the file is on a drive
that supports mixed-case filenames, and converts it to all lower-case if
it isn't. _chdir2 changes both the current working directory and drive.
_getcwd1 gets the current working directory on a drive. I depend on
several Unix functions which EMX provides, but many commercial compilers
don't. Good luck.
How to Install ME
--- -- ------- --
"make install" doesn't work. You have to
Copy me/me3 and mc/mc2 to a directory in your PATH.
Copy mutt/package/*.mco to c:/me3 or where you specified
in config.h. Or leave them where they are and use the ME3
environment variable (which is what CD does). See "load" in
me/doc/me3.doc for more about this var.
If you want the online help system to work, copy doc/*.doc and
doc/web.idx to the same place as the .mco files. (but you have to
get me34src.zip to get the docs).
As a quick test, run me, hit Escape x load <return> ganoi <return> and
use 4 disks. If you get the towers of hanoi, things are probably
working pretty good.
I have not included all the documentation. If you want to figure out
how things work, get me34src.zip, which has additional docs, and some
mutt sources which aren't included here. Look over at least me3.doc.
Patrick TJ McPhee
ptjm@io.org
Toronto Canada