Mercurial > vim

comparison runtime/doc/os_vms.txt @ 15533:08604d82fc9e v8.1.0774

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.1.0774: VMS build is missing the blob file commit https://github.com/vim/vim/commit/05a2907cde00ac3ccff01c59978f174c020cc375 Author: Bram Moolenaar <Bram@vim.org> Date: Fri Jan 18 22:59:53 2019 +0100 patch 8.1.0774: VMS build is missing the blob file Problem: VMS build is missing the blob file. Solution: Add the blob file to the build rules. (Zoltan Arpadffy)
author Bram Moolenaar <Bram@vim.org>
date Fri, 18 Jan 2019 23:00:08 +0100
parents 2f7e67dd088c
children 7cfe57329284
comparison
equal deleted inserted replaced
15532:89a1e78badbf 15533:08604d82fc9e
1 *os_vms.txt* For Vim version 8.1. Last change: 2018 May 06 1 *os_vms.txt* For Vim version 8.1. Last change: 2019 Jan 18
2 2
3 3
4 VIM REFERENCE MANUAL 4 VIM REFERENCE MANUAL
5 5
6 6
102 to set up GUI fonts etc. correctly. See :help xim from Vim command prompt. 102 to set up GUI fonts etc. correctly. See :help xim from Vim command prompt.
103 103
104 You may want to use GUI with GTK icons, then you have to download and install 104 You may want to use GUI with GTK icons, then you have to download and install
105 GTK for OpenVMS or at least runtime shareable images - LIBGTK from 105 GTK for OpenVMS or at least runtime shareable images - LIBGTK from
106 polarhome.com 106 polarhome.com
107 Post 7.2 Vim uses GTK2+ while the last GTK on OpenVMS is 1.2.10, thefore
108 the GTK build is no longer available.
107 109
108 For more advanced questions, please send your problem to Vim on VMS mailing 110 For more advanced questions, please send your problem to Vim on VMS mailing
109 list <vim-vms@polarhome.com> 111 list <vim-vms@polarhome.com>
110 More about the vim-vms list can be found at: 112 More about the vim-vms list can be found at:
111 http://www.polarhome.com/mailman/listinfo/vim-vms 113 http://www.polarhome.com/mailman/listinfo/vim-vms
199 201
200 You can check that everything is at the right place with the :version command. 202 You can check that everything is at the right place with the :version command.
201 203
202 Example LOGIN.COM: > 204 Example LOGIN.COM: >
203 205
204 $ define/nolog VIM RF10:[UTIL.VIM] 206 $ define/nolog VIM DKA0:[UTIL.VIM81]
205 $ vi*m :== mcr VIM:VIM.EXE 207 $ vi*m :== mcr VIM:VIM.EXE
206 $ gv*im:== spawn/nowait/input=NLA0 mcr VIM:VIM.EXE -g -GEOMETRY 80x40 208 $ gv*im:== spawn/nowait/input=NLA0 mcr VIM:VIM.EXE -g -GEOMETRY 80x40
207 $ set disp/create/node=192.168.5.223/trans=tcpip 209 $ set disp/create/node=192.168.10.202/trans=tcpip
208 210
209 Note: This set-up should be enough, if you are working on a standalone server or 211 Note: This set-up should be enough, if you are working on a standalone server or
210 clustered environment, but if you want to use Vim as an internode editor in 212 clustered environment, but if you want to use Vim as an internode editor in
211 DECNET environment, it will satisfy as well. 213 DECNET environment, it will satisfy as well.
212 You just have to define the "whole" path: > 214 You just have to define the "whole" path: >
761 (Zoltan Arpadffy, Vim 7.2) 763 (Zoltan Arpadffy, Vim 7.2)
762 764
763 ============================================================================== 765 ==============================================================================
764 766
765 9. VMS related changes *vms-changes* 767 9. VMS related changes *vms-changes*
768
769 Version 8.1
770 - make necessary changes to build v8.1 on VMS
771
772 Version 8.0
773 - solve the 100% cpu usage issue while waiting for a keystroke
774 - correct the VMS warnings and errors around handling the INFINITY (used in json.c)
775 - minor VMS port related changes
776 - correct the make_vms.mms file for 8.0
777 - fix [.TESTDIR]make_vms.mms for 8.0
766 778
767 Version 7.4 779 Version 7.4
768 - Undo: VMS can not handle more than one dot in the filenames use "dir/name" -> "dir/_un_name" 780 - Undo: VMS can not handle more than one dot in the filenames use "dir/name" -> "dir/_un_name"
769 add _un_ at the beginning to keep the extension 781 add _un_ at the beginning to keep the extension
770 - correct swap file name wildcard handling 782 - correct swap file name wildcard handling