nyx/vim
1
0
Fork 0
mirror of https://github.com/vim/vim synced 2025-03-21 17:25:11 +01:00
Code Issues1 Projects Releases Packages Wiki Activity Actions3
vim/runtime/ftplugin/html.vim

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

61 lines
1.9 KiB
VimL
Raw Normal View History

updated for version 7.0001
2004-06-13 20:20:40 +00:00
" Vim filetype plugin file
Update runtime files
2022-07-25 15:42:07 +01:00
" Language: HTML
" Maintainer: Doug Kearns <dougkearns@gmail.com>
" Previous Maintainer: Dan Sharp
runtime(ftplugin): Use "*" browsefilter pattern to match "All Files" Problem: The "*.*" browsefilter pattern only matches all files on Windows (Daryl Lee) Solution: Use "*" to filter on all platforms but keep "*.*" as the label text on Windows. (Fixes #12685, Doug Kearns) The *.* browsefilter pattern used to match "All Files" on Windows is a legacy of the DOS 8.3 filename wildcard matching algorithm. For reasons of backward compatibility this still works on Windows to match all files, even those without an extension. However, this pattern only matches filenames containing a dot on other platforms. This often makes files without an extension difficult to access from the file dialog, e.g., "Makefile" On Windows it is still standard practice to use "*.*" for the filter label so ftplugins should use "All Files (*.*)" on Windows and "All Files (*)" on other platforms. This matches Vim's default browsefilter values. This commit also normalises the browsefilter conditional test to check for the Win32 and GTK GUI features and an unset b:browsefilter. closes: #12759 Signed-off-by: Doug Kearns <dougkearns@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-01-14 20:59:02 +01:00
" Last Change: 2024 Jan 14
patch 9.1.0464: no whitespace padding in commentstring option in ftplugins Problem: no whitespace padding in commentstring option in ftplugins Solution: Change default to include whitespace padding, update existing filetype plugins with the new default value (Riley Bruins) closes: #14843 Signed-off-by: Riley Bruins <ribru17@hotmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-06-03 20:40:45 +02:00
" 2024 May 24 by Riley Bruins <ribru17@gmail.com> ('commentstring')
Update runtime files
2022-07-25 15:42:07 +01:00
if exists("b:did_ftplugin")
finish
endif
updated for version 7.0001
2004-06-13 20:20:40 +00:00
let b:did_ftplugin = 1
let s:save_cpo = &cpo
set cpo-=C
updated for version 7.2a
2008-06-24 20:39:31 +00:00
setlocal matchpairs+=<:>
patch 9.1.0464: no whitespace padding in commentstring option in ftplugins Problem: no whitespace padding in commentstring option in ftplugins Solution: Change default to include whitespace padding, update existing filetype plugins with the new default value (Riley Bruins) closes: #14843 Signed-off-by: Riley Bruins <ribru17@hotmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-06-03 20:40:45 +02:00
setlocal commentstring=<!--\ %s\ -->
updated for version 7.2c-000
2008-08-06 17:06:04 +00:00
setlocal comments=s:<!--,m:\ \ \ \ ,e:-->
Update runtime files
2022-07-25 15:42:07 +01:00
let b:undo_ftplugin = "setlocal comments< commentstring< matchpairs<"
if get(g:, "ft_html_autocomment", 0)
setlocal formatoptions-=t formatoptions+=croql
let b:undo_ftplugin ..= " | setlocal formatoptions<"
updated for version 7.2c-000
2008-08-06 17:06:04 +00:00
endif
updated for version 7.0f02
2006-04-27 00:02:13 +00:00
if exists('&omnifunc')
Updated runtime files.
2014-06-25 18:50:27 +02:00
setlocal omnifunc=htmlcomplete#CompleteTags
call htmlcomplete#DetectOmniFlavor()
Update runtime files
2022-07-25 15:42:07 +01:00
let b:undo_ftplugin ..= " | setlocal omnifunc<"
updated for version 7.0f02
2006-04-27 00:02:13 +00:00
endif
updated for version 7.0e07
2006-04-23 22:40:29 +00:00
Update runtime files
2022-07-25 15:42:07 +01:00
" HTML: thanks to Johannes Zellner and Benji Fisher.
if exists("loaded_matchit") && !exists("b:match_words")
let b:match_ignorecase = 1
let b:match_words = '<!--:-->,' ..
\ '<:>,' ..
\ '<\@<=[ou]l\>[^>]*\%(>\|$\):<\@<=li\>:<\@<=/[ou]l>,' ..
\ '<\@<=dl\>[^>]*\%(>\|$\):<\@<=d[td]\>:<\@<=/dl>,' ..
\ '<\@<=\([^/!][^ \t>]*\)[^>]*\%(>\|$\):<\@<=/\1>'
let b:html_set_match_words = 1
let b:undo_ftplugin ..= " | unlet! b:match_ignorecase b:match_words b:html_set_match_words"
updated for version 7.0001
2004-06-13 20:20:40 +00:00
endif
" Change the :browse e filter to primarily show HTML-related files.
Update runtime files
2022-07-25 15:42:07 +01:00
if (has("gui_win32") || has("gui_gtk")) && !exists("b:browsefilter")
runtime(ftplugin): Use "*" browsefilter pattern to match "All Files" Problem: The "*.*" browsefilter pattern only matches all files on Windows (Daryl Lee) Solution: Use "*" to filter on all platforms but keep "*.*" as the label text on Windows. (Fixes #12685, Doug Kearns) The *.* browsefilter pattern used to match "All Files" on Windows is a legacy of the DOS 8.3 filename wildcard matching algorithm. For reasons of backward compatibility this still works on Windows to match all files, even those without an extension. However, this pattern only matches filenames containing a dot on other platforms. This often makes files without an extension difficult to access from the file dialog, e.g., "Makefile" On Windows it is still standard practice to use "*.*" for the filter label so ftplugins should use "All Files (*.*)" on Windows and "All Files (*)" on other platforms. This matches Vim's default browsefilter values. This commit also normalises the browsefilter conditional test to check for the Win32 and GTK GUI features and an unset b:browsefilter. closes: #12759 Signed-off-by: Doug Kearns <dougkearns@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-01-14 20:59:02 +01:00
let b:browsefilter = "HTML Files (*.html, *.htm)\t*.html;*.htm\n" ..
Update runtime files
2022-07-25 15:42:07 +01:00
\ "JavaScript Files (*.js)\t*.js\n" ..
runtime(ftplugin): Use "*" browsefilter pattern to match "All Files" Problem: The "*.*" browsefilter pattern only matches all files on Windows (Daryl Lee) Solution: Use "*" to filter on all platforms but keep "*.*" as the label text on Windows. (Fixes #12685, Doug Kearns) The *.* browsefilter pattern used to match "All Files" on Windows is a legacy of the DOS 8.3 filename wildcard matching algorithm. For reasons of backward compatibility this still works on Windows to match all files, even those without an extension. However, this pattern only matches filenames containing a dot on other platforms. This often makes files without an extension difficult to access from the file dialog, e.g., "Makefile" On Windows it is still standard practice to use "*.*" for the filter label so ftplugins should use "All Files (*.*)" on Windows and "All Files (*)" on other platforms. This matches Vim's default browsefilter values. This commit also normalises the browsefilter conditional test to check for the Win32 and GTK GUI features and an unset b:browsefilter. closes: #12759 Signed-off-by: Doug Kearns <dougkearns@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-01-14 20:59:02 +01:00
\ "Cascading StyleSheets (*.css)\t*.css\n"
if has("win32")
let b:browsefilter ..= "All Files (*.*)\t*\n"
else
let b:browsefilter ..= "All Files (*)\t*\n"
endif
Update runtime files
2022-07-25 15:42:07 +01:00
let b:html_set_browsefilter = 1
let b:undo_ftplugin ..= " | unlet! b:browsefilter b:html_set_browsefilter"
updated for version 7.0001
2004-06-13 20:20:40 +00:00
endif
let &cpo = s:save_cpo
Updated runtime files. Add Dutch translations.
2012-03-11 15:57:40 +01:00
unlet s:save_cpo
Reference in a new issue Copy permalink