Mercurial > vim
comparison runtime/doc/os_mac.txt @ 12716:351cf7c67bbe v8.0.1236
patch 8.0.1236: Mac features are confusing
commit https://github.com/vim/vim/commit/d057301b1f28736f094affa17b190244ad56e8d9
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Oct 28 21:11:06 2017 +0200
patch 8.0.1236: Mac features are confusing
Problem: Mac features are confusing.
Solution: Make feature names more consistent, add "osxdarwin". Rename
feature flags, cleanup Mac code. (Kazunobu Kuriyama, closes #2178)
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sat, 28 Oct 2017 21:15:35 +0200 |
parents | cc5253681167 |
children | 371ceeebbdaa |
comparison
equal
deleted
inserted
replaced
12715:279ec0abb4ac | 12716:351cf7c67bbe |
---|---|
162 ./configure --disable-darwin <other options> | 162 ./configure --disable-darwin <other options> |
163 | 163 |
164 and then run `make` to build Vim. The order of the options doesn't matter. | 164 and then run `make` to build Vim. The order of the options doesn't matter. |
165 | 165 |
166 To make sure at runtime whether or not the darwin feature is compiled in, you | 166 To make sure at runtime whether or not the darwin feature is compiled in, you |
167 can use `has('macunix')` which returns 1 if the feature is compiled in; 0 | 167 can use `has('osxdarwin')` which returns 1 if the feature is compiled in; 0 |
168 otherwise. | 168 otherwise. For backwards comptibility, you can still use `macunix` instead of |
169 `osxdarwin`. | |
169 | 170 |
170 Notable use cases where `--disable-darwin` is turned out to be useful are: | 171 Notable use cases where `--disable-darwin` is turned out to be useful are: |
171 | 172 |
172 - When you want to use |x11-selection| instead of the system clipboard. | 173 - When you want to use |x11-selection| instead of the system clipboard. |
173 - When you want to use |x11-clientserver|. | 174 - When you want to use |x11-clientserver|. |