view src/INSTALLmac.txt @ 34854:97b5457962ed v9.1.0296

patch 9.1.0296: regexp: engines do not handle case-folding well Commit: https://github.com/vim/vim/commit/7a27c108e0509f3255ebdcb6558e896c223e4d23 Author: Christian Brabandt <cb@256bit.org> Date: Tue Apr 9 22:53:19 2024 +0200 patch 9.1.0296: regexp: engines do not handle case-folding well Problem: Regex engines do not handle case-folding well Solution: Correctly calculate byte length of characters to skip When the regexp engine compares two utf-8 codepoints case insensitively it may match an adjacent character, because it assumes it can step over as many bytes as the pattern contains. This however is not necessarily true because of case-folding, a multi-byte UTF-8 character can be considered equal to some single-byte value. Let's consider the pattern '?' and the string 's'. When comparing and ignoring case, the single character 's' matches, and since it matches Vim will try to step over the match (by the amount of bytes of the pattern), assuming that since it matches, the length of both strings is the same. However in that case, it should only step over the single byte value 's' so by 1 byte and try to start matching after it again. So for the backtracking engine we need to ensure: - we try to match the correct length for the pattern and the text - in case of a match, we step over it correctly The same thing can happen for the NFA engine, when skipping to the next character to test for a match. We are skipping over the regstart pointer, however we do not consider the case that because of case-folding we may need to adjust the number of bytes to skip over. So this needs to be adjusted in find_match_text() as well. A related issue turned out, when prog->match_text is actually empty. In that case we should try to find the next match and skip this condition. fixes: #14294 closes: #14433 Signed-off-by: Christian Brabandt <cb@256bit.org>
author Christian Brabandt <cb@256bit.org>
date Tue, 09 Apr 2024 23:00:08 +0200
parents 695b50472e85
children
line wrap: on
line source

INSTALLmac.txt - Installation of Vim on Apple MacOS

This file contains instructions for compiling Vim. If you already have an
executable version of Vim, you don't need this.

MacOS Classic is no longer supported.  If you really want it use Vim 6.4.
Only '/' is supported as path separator.


----------------------------------------------------------------------------
Prerequisites
----------------------------------------------------------------------------

Make sure you've installed Xcode and CommandLineTools.  You can download Xcode
from the Mac App Store, for free.

To check for CommandLineTools open a terminal and do:

	$ make --version

If not installed yet a window pops up instructing you to install the developer
tools.

If you don't have the source yet, best is to use git (which you need to
install first), see http://www.vim.org/git.php
Or you can download and unpack the Unix tar archive, see
   http://www.vim.org/download.php


----------------------------------------------------------------------------
Build and install the terminal version.
----------------------------------------------------------------------------

You can compile vim with the standard Unix routine:
   cd vim/src
   make
   make test
   sudo make install

If you get an error "glibtool: command not found" search on stackoverflow for
mac-osx-where-can-i-download-glibtool.

With Homebrew, run:

      brew install libtool

To build libtool from source:

    1. Download the source code from https://www.gnu.org/software/libtool/.

    2. Run these commands from the root of the source code directory:

           ./configure --program-prefix=g
           make
           sudo make install


----------------------------------------------------------------------------
Build and install the GUI version with X-Windows
----------------------------------------------------------------------------

NOTE: this probably no longer works, since Athena support has been removed.

First, install XQuartz, which you can download from https://www.xquartz.org.

To tell configure to use a GUI you can edit the Makefile and uncomment these
two lines (remove the # at the start of the line):

    CONF_OPT_GUI = --enable-gui=athena
    CONF_OPT_DARWIN = --disable-darwin

Do "make distclean" to start with a clean slate.
Then build as with the terminal version above.
Instead of "athena" you can try "gtk2" but you probably need to install GTK
first.


----------------------------------------------------------------------------
Notes
----------------------------------------------------------------------------

Mac-specific configure options are explained in the Makefile:
	--disable-darwin
	--with-mac-arch