diff options
| author | Bram Moolenaar <Bram@vim.org> | 2017-10-28 21:11:06 +0200 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2017-10-28 21:11:06 +0200 |
| commit | d057301b1f28736f094affa17b190244ad56e8d9 (patch) | |
| tree | ae20801354321a5ff0d7d23b04d8d6018c57645a /runtime/doc/os_mac.txt | |
| parent | ef83956e1e67736b4c6b886d897b74f022622a74 (diff) | |
patch 8.0.1236: Mac features are confusingv8.0.1236
Problem: Mac features are confusing.
Solution: Make feature names more consistent, add "osxdarwin". Rename
feature flags, cleanup Mac code. (Kazunobu Kuriyama, closes #2178)
Diffstat (limited to 'runtime/doc/os_mac.txt')
| -rw-r--r-- | runtime/doc/os_mac.txt | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/runtime/doc/os_mac.txt b/runtime/doc/os_mac.txt index cff87dec24..2a2b07a7a9 100644 --- a/runtime/doc/os_mac.txt +++ b/runtime/doc/os_mac.txt @@ -164,8 +164,9 @@ If you want to disable it, pass `--disable-darwin` to the configure script: > and then run `make` to build Vim. The order of the options doesn't matter. To make sure at runtime whether or not the darwin feature is compiled in, you -can use `has('macunix')` which returns 1 if the feature is compiled in; 0 -otherwise. +can use `has('osxdarwin')` which returns 1 if the feature is compiled in; 0 +otherwise. For backwards comptibility, you can still use `macunix` instead of +`osxdarwin`. Notable use cases where `--disable-darwin` is turned out to be useful are: |