runtime(doc): make examples verbatim to prevent conceal/tag parsing
closes: #17437 Signed-off-by: Yochem van Rosmalen <git@yochem.nl> Signed-off-by: Christian Brabandt <cb@256bit.org>
This commit is contained in:
committed by
Christian Brabandt
parent
bfeefc474a
commit
2090405de5
@ -1,4 +1,4 @@
|
||||
*editing.txt* For Vim version 9.1. Last change: 2025 Apr 03
|
||||
*editing.txt* For Vim version 9.1. Last change: 2025 Jun 03
|
||||
|
||||
|
||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
||||
@ -1342,9 +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 "All Files (*.*)\t*\n" as the final filter on Windows or "All
|
||||
Files (*)\t*\n" on other platforms, so that the user can still access any
|
||||
desired file.
|
||||
may want to add >
|
||||
|
||||
All Files\t(*.*)\t*\n
|
||||
<
|
||||
as the final filter on Windows or >
|
||||
|
||||
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"): >
|
||||
|
||||
Reference in New Issue
Block a user