From c730374d440ad32c2a57ccef3278226a87821c34 Mon Sep 17 00:00:00 2001 From: zeertzjq Date: Thu, 26 Jun 2025 08:02:53 +0800 Subject: [PATCH] vim-patch:fa0b069: runtime(doc): improve documentation style in editing.txt (#34646) 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: vim/vim#17607 https://github.com/vim/vim/commit/fa0b0697283487171981bea751f3c676399864d6 Co-authored-by: mityu Co-authored-by: Hirohito Higashi --- runtime/doc/editing.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/runtime/doc/editing.txt b/runtime/doc/editing.txt index 9a8d413181..84c3755a18 100644 --- a/runtime/doc/editing.txt +++ b/runtime/doc/editing.txt @@ -1316,15 +1316,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"): >