Vim documentation: os_390
main help file
*os_390.txt* For Vim version 6.0as. Last change: 2001 Jun 03
VIM REFERENCE MANUAL by Bram Moolenaar
*OS390* *os390*
This file contains the particularities for the OS/390 Unix version of Vim.
1) Your feedback is needed |OS390-feedback|
2) Building VIM for OS/390 Unix |OS390-building|
3) Xterm Problems |OS390-xterm|
4) Motif Problems |OS390-Motif|
5) Ctags |OS390-ctags|
6) Known weaknesses |OS390-weaknesses|
7) Changes |OS390-changes|
8) Porting VIM to OS/390 Unix |OS390-porting|
The port to OS/390 Unix was done by Ralf Schandl <schandl@de.ibm.com>.
DISCLAIMER:
Also I am an IBMer, IBM is not responsible for this port, this is my
private fun. If you have problems with this port, please contact me.
If you want to use more Open Source Software on OS/390 Unix have a look
at the following Redbook (www.redbooks.ibm.com):
Mike MacIsaak et al
"Open Source Software on OS/390 Unix"
SG24-5944-00
*OS390-feedback*
1) Your feedback is needed
A lot of changes had to be done to the code to get Vim on OS/390 Unix. As most
Unix programs it contained heavy ASCII dependencies. It might be, that I
missed a ASCII dependency or that a new one has been added with a new feature
or bug fix. Most programmers are simply not aware of possible ASCII/EBCDIC
problems. If you hit a problem, that seems related to this, feel free to
contact me at the email adress above.
Only if you report a bug, it is possible to fix it. Don't rely on someone else
reporting it! Also see the section |bug-reports|.
If you are happy with Vim on OS/390 Unix, drop me a mail too.
*OS390-building*
2) Building VIM for OS/390 Unix
A word on debugging code first:
The normal run of configure adds the flag '-g' to the compiler options,
to include debugging information into the executable. This information
are normally removed from the executable with the strip command during
installation. On OS/390 Unix, it is not possible to remove this from
the executable. The strip command exists on OS/390 Unix and is called
during the installation, but in fact it just does nothing.
If you want to build Vim without debugging code, export the environment
variable CFLAGS set to an empty string, before you call configure.
export CFLAGS=""
Building without X11:
If you build VIM without X11 support, compiling and building is
straightforward, but don't forget to export _CC_CCMODE=1 before calling
configure and make.
$ export _CC_CCMODE=1
$./configure --with-features=big --without-x --enable-gui=no
$ make
$ make test
NOTE: Test 11 will fail, if you don't have gzip installed.
Test 42 will fail, as VIM on OS/390 Unix doesn't support the multibyte
feature.
>
$ make install
<
Building with X11:
There are two ways for building VIM with X11 support. You can link it
statically with the X11 libraries or can bind it with the X11 DLLs. The
statical link results in a huge executable (~13Mb), the dynamical linked