-*develop.txt* For Vim version 9.1. Last change: 2025 Aug 08
+*develop.txt* For Vim version 9.1. Last change: 2025 Aug 10
VIM REFERENCE MANUAL by Bram Moolenaar
defined in POSIX.1-2001 `make` and ignoring later POSIX standards or GNU/BSD
extensions. In practical terms, avoid:
- – % pattern rules
- – modern assignment (`:=`, `::=`) outside POSIX.1-2001
- – special targets (`.ONESHELL`, `.NOTPARALLEL`, `.SILENT`, …)
- – order-only prerequisites (`|`) or automatic directory creation
- – GNU/BSD conditionals (`ifdef`, `ifndef`, `.for`/`.endfor`, …)
+ - % pattern rules
+ - modern assignment (`:=`, `::=`) outside POSIX.1-2001
+ - special targets (`.ONESHELL`, `.NOTPARALLEL`, `.SILENT`, ...)
+ - order-only prerequisites (`|`) or automatic directory creation
+ - GNU/BSD conditionals (`ifdef`, `ifndef`, `.for`/`.endfor`, ...)
Since POSIX.1-2001 supports only traditional suffix rules, every object built
in a separate directory must have an explicit rule. For example:
`C95` (ISO/IEC 9899:1990/AMD1:1995)
In addition, the following `C99` features are explicitly allowed:
- – logical lines may contain up to 4095 characters;
- – `//` comments, as required by |style-comments|;
- – the `_Bool` type.
+ - `//` comments, as required by |style-comments|;
+ - the `_Bool` type.
+ - logical lines may contain up to 4095 characters;
Platform-specific code may use any newer compiler features supported on that
platform.
SIZE OF VARIABLES *assumptions-variables*
-We follow POSIX.1‑2001 (SUSv3) for type sizes, which in practice means:
+We follow POSIX.1-2001 (SUSv3) for type sizes, which in practice means:
- char_u 8-bit unsigned
- int ≥ 32-bit signed
- unsigned ≥ 32-bit unsigned
+ char_u 8-bit unsigned
+ int 32-bit or larger signed
+ unsigned 32-bit or larger unsigned
==============================================================================
-*filetype.txt* For Vim version 9.1. Last change: 2025 Aug 06
+*filetype.txt* For Vim version 9.1. Last change: 2025 Aug 10
VIM REFERENCE MANUAL by Bram Moolenaar
]" move to the next (legacy) comment
[" move to the previous (legacy) comment
gf edit the file under the cursor
- CTRL-W gf edit the file under the cursor in a new tab
+ CTRL-W gf edit the file under the cursor in a new tab page
CTRL-W f edit the file under the cursor in a new window
" Vim filetype plugin
" Language: Vim
" Maintainer: Doug Kearns <dougkearns@gmail.com>
-" Last Change: 2025 Aug 07
" Former Maintainer: Bram Moolenaar <Bram@vim.org>
" Contributors: Riley Bruins <ribru17@gmail.com> ('commentstring')
" @Konfekt
" @tpope (s:Help())
" @lacygoill
-" Last Change: 2025 Mar 05
+" Last Change: 2025 Aug 07
" 2025 Aug 06 by Vim Project (add gf maps #17881)
-" 2025 Aug 08 by Vim Project (add vimscript complete function #17871)
+" 2025 Aug 08 by Vim Project (add Vim script complete function #17871)
" Only do this when not done yet for this buffer
if exists("b:did_ftplugin")
-*helptoc.txt* For Vim version 9.1. Last change: 2025 Aug 06
+*helptoc.txt* For Vim version 9.1. Last change: 2025 Aug 10
VIM REFERENCE MANUAL
3.7 vim *HelpToc-vim-filetype*
-Vimscript and Vim9 script do not have headings or levels inherently like
+Vim script and Vim9 script do not have headings or levels inherently like
markup languages. However, Vim provides for |folds| defined by markers (|{{{|),
which themselves may be succeeded by a number explicitly indicating the fold
level. This is the structure recognized and supported by helptoc.vim.