mirrors/neovim
1
0
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2025-09-06 03:18:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

vim-patch:partial:624bb83: runtime(doc): Tweak documentation style a bit (#31148)

Browse Source 
closes: vim/vim#11419

624bb83619

Skip syncolor.vim and v:colornames

Co-authored-by: h-east <h.east.727@gmail.com>
This commit is contained in:
zeertzjq
2024-11-10 09:11:06 +08:00
committed by GitHub
parent 7d8dd8234a
commit 7232b54aee
5 changed files with 46 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
runtime/doc/filetype.txt
View File

@@ -1046,8 +1046,8 @@ To enable: >
let g:typst_folding = 1 let g:typst_folding = 1
< <
*g:typst_foldnested* *g:typst_foldnested*
When |TRUE| the Typst filetype plugin will fold nested heading under their parents When |TRUE| the Typst filetype plugin will fold nested heading under their
(default: |TRUE|) parents. (default: |TRUE|)
To disable: > To disable: >
let g:typst_foldnested = 0 let g:typst_foldnested = 0

45
runtime/doc/syntax.txt
View File

@@ -1209,20 +1209,20 @@ on" command in your .vimrc file.
When you edit an existing Fortran file, the syntax script will assume free When you edit an existing Fortran file, the syntax script will assume free
source form if the fortran_free_source variable has been set, and assumes source form if the fortran_free_source variable has been set, and assumes
fixed source form if the fortran_fixed_source variable has been set. Suppose fixed source form if the fortran_fixed_source variable has been set. Suppose
neither of these variables have been set. In that case, the syntax script attempts to neither of these variables have been set. In that case, the syntax script
determine which source form has been used by examining the file extension attempts to determine which source form has been used by examining the file
using conventions common to the ifort, gfortran, Cray, NAG, and PathScale extension using conventions common to the ifort, gfortran, Cray, NAG, and
compilers (.f, .for, .f77 for fixed-source, .f90, .f95, .f03, .f08 for PathScale compilers (.f, .for, .f77 for fixed-source, .f90, .f95, .f03, .f08
free-source). No default is used for the .fpp and .ftn file extensions because for free-source). No default is used for the .fpp and .ftn file extensions
different compilers treat them differently. If none of this works, then the because different compilers treat them differently. If none of this works,
script examines the first five columns of the first 500 lines of your file. If then the script examines the first five columns of the first 500 lines of your
no signs of free source form are detected, then the file is assumed to be in file. If no signs of free source form are detected, then the file is assumed
fixed source form. The algorithm should work in the vast majority of cases. to be in fixed source form. The algorithm should work in the vast majority of
In some cases, such as a file that begins with 500 or more full-line comments, cases. In some cases, such as a file that begins with 500 or more full-line
the script may incorrectly decide that the code is in fixed form. If that comments, the script may incorrectly decide that the code is in fixed form.
happens, just add a non-comment statement beginning anywhere in the first five If that happens, just add a non-comment statement beginning anywhere in the
columns of the first twenty-five lines, save (:w), and then reload (:e!) the first five columns of the first twenty-five lines, save (:w), and then reload
file. (:e!) the file.
Vendor extensions ~ Vendor extensions ~
Fixed-form Fortran requires a maximum line length of 72 characters but the Fixed-form Fortran requires a maximum line length of 72 characters but the
@@ -1753,9 +1753,9 @@ define the vim variable 'lace_case_insensitive' in your startup file: >
LF (LFRC) *lf.vim* *ft-lf-syntax* *g:lf_shell_syntax* LF (LFRC) *lf.vim* *ft-lf-syntax* *g:lf_shell_syntax*
*b:lf_shell_syntax* *b:lf_shell_syntax*
For the lf file manager configuration files (lfrc) the shell commands For the lf file manager configuration files (lfrc) the shell commands syntax
syntax highlighting can be changed globally and per buffer by setting highlighting can be changed globally and per buffer by setting a different
a different 'include' command search pattern using these variables: 'include' command search pattern using these variables: >
let g:lf_shell_syntax = "syntax/dosbatch.vim" let g:lf_shell_syntax = "syntax/dosbatch.vim"
let b:lf_shell_syntax = "syntax/zsh.vim" let b:lf_shell_syntax = "syntax/zsh.vim"
@@ -2065,9 +2065,10 @@ set "msql_minlines" to the value you desire. Example: >
:let msql_minlines = 200 :let msql_minlines = 200
NEOMUTT *neomutt.vim* *ft-neomuttrc-syntax* *ft-neomuttlog-syntax* NEOMUTT *neomutt.vim* *ft-neomuttrc-syntax*
*ft-neomuttlog-syntax*
To disable the default NeoMutt log colors > To disable the default NeoMutt log colors: >
:let g:neolog_disable_default_colors = 1 :let g:neolog_disable_default_colors = 1
@@ -2236,9 +2237,9 @@ specified. Default = 1 >
:let g:pandoc#syntax#codeblocks#embeds#use = 1 :let g:pandoc#syntax#codeblocks#embeds#use = 1
For specify what languages and using what syntax files to highlight embeds. This is a For specify what languages and using what syntax files to highlight embeds.
list of language names. When the language pandoc and vim use don't match, you This is a list of language names. When the language pandoc and vim use don't
can use the "PANDOC=VIM" syntax. For example: > match, you can use the "PANDOC=VIM" syntax. For example: >
:let g:pandoc#syntax#codeblocks#embeds#langs = ["ruby", "bash=sh"] :let g:pandoc#syntax#codeblocks#embeds#langs = ["ruby", "bash=sh"]