From: mityu Date: Wed, 25 Jun 2025 18:46:34 +0000 (+0200) Subject: runtime(doc): improve documentation style in editing.txt X-Git-Tag: v9.1.1481~1 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=fa0b0697283487171981bea751f3c676399864d6;p=thirdparty%2Fvim.git runtime(doc): improve documentation style in editing.txt Usually, Vim's document provides example code after explanations. However some part of the editing.txt doesn't follow the style, therefore this commit modifies it so that it follows the usual style. closes: #17607 Co-authored-by: Hirohito Higashi Signed-off-by: mityu Signed-off-by: Hirohito Higashi Signed-off-by: Christian Brabandt --- diff --git a/runtime/doc/editing.txt b/runtime/doc/editing.txt index dbb991e56b..270cc9e246 100644 --- a/runtime/doc/editing.txt +++ b/runtime/doc/editing.txt @@ -1,4 +1,4 @@ -*editing.txt* For Vim version 9.1. Last change: 2025 Jun 04 +*editing.txt* For Vim version 9.1. Last change: 2025 Jun 25 VIM REFERENCE MANUAL by Bram Moolenaar @@ -1342,15 +1342,15 @@ b:browsefilter variable. You would most likely set b:browsefilter in a filetype plugin, so that the browse dialog would contain entries related to the type of file you are currently editing. Disadvantage: This makes it difficult to start editing a file of a different type. To overcome this, you -may want to add > +can add the following as the final filter on Windows: > All Files\t(*.*)\t*\n < -as the final filter on Windows or > +Or the following on other platforms, so that the user can still access any +desired file: > All Files\t(*)\t*\n < -on other platforms, so that the user can still access any desired file. To avoid setting browsefilter when Vim does not actually support it, you can use has("browsefilter"): >