| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Need a new release
Solution: Release Vim 9.1
Signed-off-by: Christian Brabandt <cb@256bit.org>
|
|
Problem: MS-Windows: context menu translations may be wrong.
Solution: Set the encoding before using gettext(). (Ken Takata,
closes #12441, closes #12431)
|
|
Problem: Various typos.
Solution: Correct typos. (closes #11432)
|
|
Problem: MS-Windows makefiles are inconsistently named.
Solution: Use consistent names. (Ken Takata, closes #11088)
|
|
Problem: About time to release Vim 9.0.
Solution: Update the version number everywhere.
|
|
Problem: Cannot build with clang on MS-Windows.
Solution: Add support for building with clang. (Yegappan Lakshmanan,
closes #10557)
|
|
Problem: MS-Windows: Support for MSVC 2003 is not useful.
Solution: Remove the exceptions for MSVC 2003. (Ken Takata, closes #9616)
|
|
Problem: MS-Windows: wrong working directory when opening two files with
right-click context menu. (Gabriel Dupras)
Solution: Use the working directory and pass it on to the process creation.
(Nir Lichtman, closes #9382, closes #8874)
|
|
Problem: MS-Windows: the "edit with multiple Vim" choice is not that
useful.
Solution: Change it to "Edit with multiple tabs". (Michael Soyka,
closes #8645)
|
|
Problem: MinGW: "--preprocessor" flag no longer supported.
Solution: Remove the flag, use the defaults. (Christopher Wellons,
closes #7741)
|
|
Problem: MS-Windows: setting $LANG in gvimext only causes problems.
Solution: Do not set $LANG. (Ken Takata, closes #7325)
|
|
Problem: MS-Windows: various warnings.
Solution: Set the charset to utf-8. Add _WIN32_WINNT and _USING_V110_SDK71_.
(Ken Takata, closes #5625)
|
|
|
|
Problem: Missing a few changes for the renamed files.
Solution: Rename in a few more places. (Ken Takata)
|
|
Problem: MS-Windows: Including shlguid.h causes problems for msys2.
Solution: Do not include shlguid.h. (closes #4913)
|
|
Problem: Borland support is outdated and doesn't work.
Solution: Remove Borland support, there are other (free) compilers
available. (Thomas Dziedzic, Ken Takata, closes #4364)
|
|
Problem: Compiler warning with VS2019.
Solution: Specify different offset for "AMD64". (closes #4235)
|
|
Problem: No support for Windows on ARM64.
Solution: Add ARM64 support (Leendert van Doorn)
|
|
Problem: Macros for MS-Windows are inconsistent, using "32", "3264 and
others.
Solution: Use MSWIN for all MS-Windows builds. Use FEAT_GUI_MSWIN for the
GUI build. (Hirohito Higashi, closes #3932)
|
|
Problem: A few compiler warnings.
Solution: Add type casts. (Mike Williams)
|
|
Problem: Compilation error in gvimext.cpp.
Solution: Return a value. Also fix using uninitialized variable.
|
|
Problem: GvimExt: realloc() failing is not handled properly.
Solution: Check for NULL return. (Jan-Jaap Korpershoek, closes #3689)
|
|
Problem: "Edit with existing Vim" list can get long.
Solution: Move the list to a submenu. (Ken Takata, closes #3561)
|
|
Update version number and information. Fix a couple of tests.
|
|
Problem: MS-Windows: missing 32 and 64 bit files in installer.
Solution: Include both 32 and 64 bit GvimExt and related dll files. Remove
old Windows code from the installer. (Ken Takata, closes #2144)
|
|
Problem: Using old compiler on MS-Windows.
Solution: Switch default build on MS-Windows to use MSVC 2015. (Ken Takata)
|
|
Problem: win32.mak no longer included in Windows SDK.
Solution: Do not include win32.mak. (Ken Takata)
|
|
Problem: Cannot build with new MSVC version VS2017.
Solution: Change the compiler arguments. (Leonardo Manera, closes #1731,
closes #1747)
|
|
Problem: Code for MS-Windows is complicated because of the exceptions for
old systems.
Solution: Drop support for MS-Windows older than Windows XP. (Ken Takata)
|
|
|
|
Problem: Can't build GvimExt with MingW.
Solution: Adjust the makefile. (Ben Fritz)
|
|
Problem: GvimExt only loads the old libintl.dll.
Solution: Also try loading libint-8.dll. (Ken Takata, closes #608)
|
|
Problem: Visual studio tools are noisy.
Solution: Suppress startup info. (Mike Williams)
|
|
Problem: Cygwin makefiles are unused.
Solution: Remove them.
|
|
Problem: Can't build GvimExt with SDK 7.1.
Solution: Support using setenv.bat instead of vcvars32.bat. (Ken Takata)
|
|
Problem: Building GvimExt with VS2015 may fail.
Solution: Adjust the makefile. (Mike Williams)
|
|
Problem: Cannot build GvimExt with MingW.
Solution: Add -lgdi32. (KF Leong)
|
|
Problem: Cannot build GvimExt.
Solution: Set APPVER to 5.0. (KF Leong)
|
|
Problem: Vim icon does not show in Windows context menu. (issue 249)
Solution: Load the icon in GvimExt.
|
|
Problem: The -mno-cygwin argument is no longer supported by Cygwin.
Solution: Remove the arguments. (Steve Hall)
|
|
|
|
|
|
|
|
Problem: Typos in source files.
Solution: Fix the typos. (Ken Takata)
|
|
Problem: Can't always find Win32.mak when building GvimExt.
Solution: Use same mechanism as in Make_mvc.mak. (Cade Foster)
|
|
|
|
Problem: MingW 4.6 no longer supports the -mno-cygwin option.
Solution: Split the Cygwin and MingW makefiles. (Matsushita Shougo)
|
|
Problem: GvimExt sets $LANG in the wrong way.
Solution: Save the environment and use it for gvim. (Yasuhiro Matsumoto)
|
|
Problem: MS-Windows: The edit with existing vim context menu entries can be
unwanted.
Solution: Let a registry entry disable them. (Jerome Vuarand)
|
|
Problem: Warning for building GvimExt.
Solution: Comment-out the DESCRIPTION line. (Mike Williams)
|
