summaryrefslogtreecommitdiffstats
path: root/src/Make_vms.mms
AgeCommit message (Collapse)Author
2024-01-04patch 9.1.0005: OpenVMS does not support python3 and xterm_savev9.1.0005Zoltan Arpadffy
Problem: OpenVMS build does not support python3 and xterm_save Solution: Enable python3 + xterm_save feature, fix style issues (Zoltan Arpadffy) closes: #13812 Signed-off-by: Zoltan Arpadffy <zoltan.arpadffy@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-12-19patch 9.0.2180: POSIX function name in exarg causes issuesv9.0.2180Zoltan Arpadffy
Problem: POSIX function name in exarg struct causes issues on OpenVMS Solution: Rename getline member in exarg struct to ea_getline, remove isinf() workaround for VMS There are compilers that do not treat well POSIX functions - like getline - usage in the structs. Older VMS compilers could digest this... but the newer OpenVMS compilers ( like VSI C x86-64 X7.4-843 (GEM 50XB9) ) cannot deal with these structs. This could be limited to getline() that is defined via getdelim() and might not affect all POSIX functions in general - but avoiding POSIX function names usage in the structs is a "safe side" practice without compromising the functionality or the code readability. The previous OpenVMS X86 port used a workaround limiting the compiler capabilities using __CRTL_VER_OVERRIDE=80400000 In order to make the OpenVMS port future proof, this pull request proposes a possible solution. closes: #13704 Signed-off-by: Zoltan Arpadffy <zoltan.arpadffy@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-12-05patch 9.0.2153: no support to build on OpenVMSv9.0.2153Zoltan Arpadffy
Problem: no support to build on OpenVMS Solution: Add OpenVMS X86_64 platform port closes: #13623 Co-authored-by: errael <errael@raelity.com> Co-authored-by: K.Takata <kentkt@csc.jp> Signed-off-by: Zoltan Arpadffy <zoltan.arpadffy@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2022-12-04patch 9.0.1001: classes are not documented or implemented yetv9.0.1001Bram Moolenaar
Problem: Classes are not documented or implemented yet. Solution: Make the first steps at documenting Vim9 objects, classes and interfaces. Make initial choices for the syntax. Add a skeleton implementation. Add "public" and "this" in the command table.
2022-11-30patch 9.0.0977: it is not easy to see what client-server commands are doingv9.0.0977Bram Moolenaar
Problem: It is not easy to see what client-server commands are doing. Solution: Add channel log messages if ch_log() is available. Move the channel logging and make it available with the +eval feature.
2022-10-08patch 9.0.0700: there is no real need for a "big" buildv9.0.0700Martin Tournoij
Problem: There is no real need for a "big" build. Solution: Move common features to "normal" build, less often used features to the "huge" build. (Martin Tournoij, closes #11283)
2022-10-04patch 9.0.0657: too many #ifdefsv9.0.0657Martin Tournoij
Problem: Too many #ifdefs. Solution: Graduate the +cmdwin feature. Now the tiny and small builds are equal, drop the small build. (Martin Tournoij, closes #11268)
2022-01-31patch 8.2.4270: generating nv_cmdidxs.h requires building Vim twicev8.2.4270ichizok
Problem: Generating nv_cmdidxs.h requires building Vim twice. Solution: Move the table into a separate file and use a separate executable to extract the command characters. (Ozaki Kiichi, closes #9669)
2022-01-29patch 8.2.4252: generating the normal command table at runtime is inefficientv8.2.4252Yegappan Lakshmanan
Problem: Generating the normal command table at runtime is inefficient. Solution: Generate the table with a Vim script and put it in a header file. (Yegappan Lakshmanan, closes #9648)
2022-01-13patch 8.2.4081: CodeQL reports problem in if_cscope causing it to failv8.2.4081ichizok
Problem: CodeQL reports problem in if_cscope causing it to fail. Solution: Use execvp() instead of execl(). Merge the header file into the source file. (Ozaki Kiichi, closes #9519)
2021-12-20patch 8.2.3860: Vim9: codecov struggles with the file sizev8.2.3860Bram Moolenaar
Problem: Vim9: codecov struggles with the file size. Solution: Split vim9compile.c into four files.
2021-11-19patch 8.2.3620: memory leak reported in libtlibv8.2.3620Bram Moolenaar
Problem: Memory leak reported in libtlib. Solution: Call del_curterm() when cleaning up memory. Rename term.h to termdefs.h to avoid a name clash.
2021-08-06patch 8.2.3301: memory allocation functions don't have their own placev8.2.3301Yegappan Lakshmanan
Problem: Memory allocation functions don't have their own place. Solution: Move memory allocation functions to alloc.c. (Yegappan Lakshmanan, closes #8717)
2021-07-10patch 8.2.3139: functions for string manipulation are spread outv8.2.3139Yegappan Lakshmanan
Problem: Functions for string manipulation are spread out. Solution: Move string related functions to a new source file. (Yegappan Lakshmanan, closes #8470)
2021-06-02patch 8.2.2928: the evalfunc.c file is too bigv8.2.2928Yegappan Lakshmanan
Problem: The evalfunc.c file is too big. Solution: Move float related functionality to a separate file. (Yegappan Lakshmanan, closes #8287)
2021-01-04patch 8.2.2294: VMS: a few remaining problemsv8.2.2294Bram Moolenaar
Problem: VMS: a few remaining problems. Solution: Add VMS specific changes. Add Lua support. (Zoltan Arpadffy)
2020-12-30patch 8.2.2247: VMS: various smaller problemsv8.2.2247Bram Moolenaar
Problem: VMS: various smaller problems. Solution: Fix VMS building and other problems. (Zoltan Arpadffy)
2020-08-13patch 8.2.1444: error messages are spread out and names can be confusingv8.2.1444Bram Moolenaar
Problem: Error messages are spread out and names can be confusing. Solution: Start moving error messages to a separate file and use clear names.
2020-07-22patch 8.2.1269: language and locale code spread outv8.2.1269Bram Moolenaar
Problem: Language and locale code spread out. Solution: Move relevant code to src/locale.c. (Yegappan Lakshmanan, closes #6509)
2020-07-21patch 8.2.1262: src/ex_cmds.c file is too bigv8.2.1262Bram Moolenaar
Problem: src/ex_cmds.c file is too big. Solution: Move help related code to src/help.c. (Yegappan Lakshmanan, closes #6506)
2020-06-28patch 8.2.1078: highlight and match functionality together in one filev8.2.1078Bram Moolenaar
Problem: Highlight and match functionality together in one file. Solution: Move match functionality to a separate file. (Yegappan Lakshmanan, closes #6352)
2020-06-01patch 8.2.0872: XIM code is mixed with multi-byte codev8.2.0872Bram Moolenaar
Problem: XIM code is mixed with multi-byte code. Solution: Move the XIM code to a separate file. (Yegappan Lakshmanan, closes #6177)
2020-05-30patch 8.2.0847: typval related code is spread outv8.2.0847Bram Moolenaar
Problem: Typval related code is spread out. Solution: Move code to new typval.c file. (Yegappan Lakshmanan, closes #6093)
2020-05-01patch 8.2.0674: some source files are too bigv8.2.0674Bram Moolenaar
Problem: Some source files are too big. Solution: Move text formatting functions to a new file. (Yegappan Lakshmanan, closes #6021)
2020-04-29patch 8.2.0660: the search.c file is a bit bigv8.2.0660Bram Moolenaar
Problem: The search.c file is a bit big. Solution: Split off the text object code to a separate file. (Yegappan Lakshmanan, closes #6007)
2020-04-05patch 8.2.0516: client-server code is spread outv8.2.0516Bram Moolenaar
Problem: Client-server code is spread out. Solution: Move client-server code to a new file. (Yegappan Lakshmanan, closes #5885)
2020-03-24patch 8.2.0443: clipboard code is spread outv8.2.0443Bram Moolenaar
Problem: Clipboard code is spread out. Solution: Move clipboard code to its own file. (Yegappan Lakshmanan, closes #5827)
2020-02-14patch 8.2.0256: time and timer related code is spread outv8.2.0256Bram Moolenaar
Problem: Time and timer related code is spread out. Solution: Move time and timer related code to a new file. (Yegappan Lakshmanan, closes #5604)
2020-02-13patch 8.2.0255: VMS: missing files in buildv8.2.0255Bram Moolenaar
Problem: VMS: missing files in build. Solution: Add the files. (Zoltan Arpadffy)
2020-01-26patch 8.2.0156: various typos in source files and testsv8.2.0156Bram Moolenaar
Problem: Various typos in source files and tests. Solution: Fix the typos. (Emir Sari, closes #5532)
2019-12-14patch 8.2.0003: Build file dependencies are incompletev8.2.0003Bram Moolenaar
Problem: Build file dependencies are incomplete. Solution: Fix the dependencies. (Ken Takata, closes #5356)
2019-12-09patch 8.1.2413: cannot update ex_cmdidxs.h on MS-Windowsv8.1.2413Bram Moolenaar
Problem: Cannot update ex_cmdidxs.h on MS-Windows. Solution: Add build rules and dependencies. (Ken Takata, closes #5337)
2019-11-30patch 8.1.2370: build problems on VMSv8.1.2370Bram Moolenaar
Problem: Build problems on VMS. Solution: Adjust the build file. (Zoltan Arpadffy)
2019-11-21patch 8.1.2328: a few hangul input pieces remainv8.1.2328Bram Moolenaar
Problem: A few hangul input pieces remain. Solution: Update VMS makefile.
2019-10-09patch 8.1.2127: the indent.c file is a bit bigv8.1.2127Bram Moolenaar
Problem: The indent.c file is a bit big. Solution: Move C-indent code a a new cindent.c file. Move other indent-related code to indent.c. (Yegappan Lakshmanan, closes #5031)
2019-09-28patch 8.1.2094: the fileio.c file is too bigv8.1.2094Bram Moolenaar
Problem: The fileio.c file is too big. Solution: Move buf_write() to bufwrite.c. (Yegappan Lakshmanan, closes #4990)
2019-09-27patch 8.1.2082: some files have a weird name to fit in 8.3 charactersv8.1.2082Bram Moolenaar
Problem: Some files have a weird name to fit in 8.3 characters. Solution: Use a nicer names.
2019-09-27patch 8.1.2081: the spell.c file is too bigv8.1.2081Bram Moolenaar
Problem: The spell.c file is too big. Solution: Move the code for spell suggestions to a separate file. (Yegappan Lakshmanan, closes #4988)
2019-09-25patch 8.1.2077: the ops.c file is too bigv8.1.2077Bram Moolenaar
Problem: The ops.c file is too big. Solution: Move code for dealing with registers to a new file. (Yegappan Lakshmanan, closes #4982)
2019-09-21patch 8.1.2062: the mouse code is spread outv8.1.2062Bram Moolenaar
Problem: The mouse code is spread out. Solution: Move all the mouse code to mouse.c. (Yegappan Lakshmanan, closes #4959)
2019-09-19patch 8.1.2057: the screen.c file is much too bigv8.1.2057Bram Moolenaar
Problem: The screen.c file is much too big. Solution: Split it in three parts. (Yegappan Lakshmanan, closes #4943)
2019-09-16patch 8.1.2045: the option.c file is too bigv8.1.2045Bram Moolenaar
Problem: The option.c file is too big. Solution: Split off the code dealing with strings. (Yegappan Lakshmanan, closes #4937)
2019-09-12patch 8.1.2022: the option.c file is too bigv8.1.2022Bram Moolenaar
Problem: The option.c file is too big. Solution: Move option definitions to a separate file. (Yegappan Lakshmanan, closes #4918)
2019-09-07patch 8.1.2001: some source files are too bigv8.1.2001Bram Moolenaar
Problem: Some source files are too big. Solution: Move buffer and window related functions to evalbuffer.c and evalwindow.c. (Yegappan Lakshmanan, closes #4898)
2019-09-04patch 8.1.1979: code for handling file names is spread outv8.1.1979Bram Moolenaar
Problem: Code for handling file names is spread out. Solution: Move code to new filepath.c file. Graduate FEAT_MODIFY_FNAME.
2019-08-27patch 8.1.1933: the eval.c file is too bigv8.1.1933Bram Moolenaar
Problem: The eval.c file is too big. Solution: Move code related to variables to evalvars.c. (Yegappan Lakshmanan, closes #4868)
2019-08-25patch 8.1.1927: code for dealing with script files is spread outv8.1.1927Bram Moolenaar
Problem: Code for dealing with script files is spread out. Solution: Move the code to scriptfile.c. (Yegappan Lakshmanan, closes #4861)
2019-08-18patch 8.1.1886: command line expansion code is spread outv8.1.1886Bram Moolenaar
Problem: Command line expansion code is spread out. Solution: Move the code to cmdexpand.c. (Yegappan Lakshmanan, closes #4831)
2019-08-17patch 8.1.1869: code for the argument list is spread outv8.1.1869Bram Moolenaar
Problem: Code for the argument list is spread out. Solution: Put argument list code in arglist.c. (Yegappan Lakshmanan, closes #4819)
2019-08-06patch 8.1.1823: command line history code is spread outv8.1.1823Bram Moolenaar
Problem: Command line history code is spread out. Solution: Put the code in a new file. (Yegappan Lakshmanan, closes #4779) Also graduate the +cmdline_hist feature.