From: Christian Brabandt Date: Thu, 8 Jan 2026 21:39:15 +0000 (+0000) Subject: runtime(doc): clarify the behaviour of 'fo-m' X-Git-Tag: v9.1.2069~2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=cf8e378f4ef8e67f1ed7c3956ccfcd5bc9999e22;p=thirdparty%2Fvim.git runtime(doc): clarify the behaviour of 'fo-m' fixes: #19095 Signed-off-by: Christian Brabandt --- diff --git a/runtime/doc/change.txt b/runtime/doc/change.txt index 172bf494a6..9096b2e312 100644 --- a/runtime/doc/change.txt +++ b/runtime/doc/change.txt @@ -1,4 +1,4 @@ -*change.txt* For Vim version 9.1. Last change: 2025 Dec 18 +*change.txt* For Vim version 9.1. Last change: 2026 Jan 08 VIM REFERENCE MANUAL by Bram Moolenaar @@ -1777,7 +1777,9 @@ l Long lines are not broken in insert mode: When a line was longer than automatically format it. *fo-m* m Also break at a multibyte character above 255. This is useful for - Asian text where every character is a word on its own. + Asian text where every character is a word on its own. Note that + line breaks may also be added after punctuation characters such as + colons to match the CJK linebreaking rules. *fo-M* M When joining lines, don't insert a space before or after a multibyte character. Overrules the 'B' flag.