Mercurial > vim

view src/INSTALLmac.txt @ 33420:aa7cd2253130 v9.0.1968

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 9.0.1968: cmdline completion should consider key option Commit: https://github.com/vim/vim/commit/6ee7b521fa7531ef356ececc8be7575c3800f872 Author: Yee Cheng Chin <ychin.git@gmail.com> Date: Sun Oct 1 09:13:22 2023 +0200 patch 9.0.1968: cmdline completion should consider key option Problem: cmdline completion should consider key option Solution: Disable cmdline completion for key option, slightly refactor how P_NO_CMD_EXPAND is handled Harden crypto 'key' option: turn off cmdline completion, disable set-= "set-=" can be used maliciously with a crypto key, as it allows an attacker (who either has access to the computer or a plugin author) to guess a substring by observing the modified state. Simply turn off set+=/-=/^= for this option as there is no good reason for them to be used. Update docs to make that clear as well. Also, don't allow cmdline completion for 'key' as it just shows ***** which is not useful and confusing to the user what it means (if the user accidentally hits enter they will have replaced their key with "*****" instead). Move logic to better location, don't use above 32-bit for flags Move P_NO_CMD_EXPAND to use the unused 0x20 instead of going above 32-bits, as currently the flags parameter is only 32-bits on some systems. Left a comment to warn that future additions will need to change how the flags work either by making it 64-bit or split into two member vars. Also, move the logic for detecting P_NO_CMD_EXPAND earlier so it's not up to each handler to decide, and you won't see the temporary "..." that Vim shows while waiting for completion handler to complete. closes: #13224 Signed-off-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Yee Cheng Chin <ychin.git@gmail.com>
author Christian Brabandt <cb@256bit.org>
date Sun, 01 Oct 2023 09:30:03 +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