thac0/vim
1
0
Fork 0
forked from aniani/vim
Code Activity
Files
32b7e3a8c99d369b02154df74cbe42a37c7c7e68
vim/runtime/ftplugin/c.vim

78 lines
2.5 KiB
VimL
Raw Normal View History

updated for version 7.0001
2004-06-13 20:20:40 +00:00
" Vim filetype plugin file
" Language: C
Farewell to Bram and dedicate upcoming Vim 9.1 to him (#12749) * Dedicate upcoming Vim 9.1 to Bram Also replace in a few more places Brams email address and mention new maintainers. * Remove Bram from any Maintainer role * runtime: Align Header * it's mailing list not mailinglist
2023-08-13 10:33:05 +02:00
" Maintainer: The Vim Project <https://github.com/vim/vim>
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: 2023 Aug 22
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 Jun 02 by Riley Bruins <ribru17@gmail.com> ('commentstring')
Farewell to Bram and dedicate upcoming Vim 9.1 to him (#12749) * Dedicate upcoming Vim 9.1 to Bram Also replace in a few more places Brams email address and mention new maintainers. * Remove Bram from any Maintainer role * runtime: Align Header * it's mailing list not mailinglist
2023-08-13 10:33:05 +02:00
" Former Maintainer: Bram Moolenaar <Bram@vim.org>
updated for version 7.0001
2004-06-13 20:20:40 +00:00
" Only do this when not done yet for this buffer
if exists("b:did_ftplugin")
finish
endif
" Don't load another plugin for this buffer
let b:did_ftplugin = 1
updated for version 7.0065
2005-03-28 20:58:01 +00:00
" Using line continuation here.
updated for version 7.0090
2005-06-22 22:35:10 +00:00
let s:cpo_save = &cpo
updated for version 7.0001
2004-06-13 20:20:40 +00:00
set cpo-=C
Update runtime files.
2020-02-04 22:53:05 +01:00
let b:undo_ftplugin = "setl fo< com< ofu< cms< def< inc< | if has('vms') | setl isk< | endif"
updated for version 7.0001
2004-06-13 20:20:40 +00:00
" Set 'formatoptions' to break comment lines but not other lines,
" and insert the comment leader when hitting <CR> or using "o".
setlocal fo-=t fo+=croql
Update runtime files.
2020-02-04 22:53:05 +01:00
" These options have the right value as default, but the user may have
" overruled that.
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\ */ define& include&
Update runtime files.
2020-02-04 22:53:05 +01:00
updated for version 7.0140
2005-09-01 20:46:49 +00:00
" Set completion with CTRL-X CTRL-O to autoloaded function.
if exists('&ofu')
setlocal ofu=ccomplete#Complete
endif
updated for version 7.0001
2004-06-13 20:20:40 +00:00
" Set 'comments' to format dashed lists in comments.
Update runtime files
2022-04-08 17:45:08 +01:00
" Also include ///, used for Doxygen.
setlocal comments=sO:*\ -,mO:*\ \ ,exO:*/,s1:/*,mb:*,ex:*/,:///,://
updated for version 7.0001
2004-06-13 20:20:40 +00:00
" In VMS C keywords contain '$' characters.
if has("vms")
setlocal iskeyword+=$
endif
updated for version 7.2a
2008-06-24 21:56:24 +00:00
" When the matchit plugin is loaded, this makes the % command skip parens and
Long overdue runtime update.
2017-11-02 22:58:42 +01:00
" braces in comments properly.
Update runtime files
2021-09-21 20:09:51 +02:00
if !exists("b:match_words")
let b:match_words = '^\s*#\s*if\(\|def\|ndef\)\>:^\s*#\s*elif\>:^\s*#\s*else\>:^\s*#\s*endif\>'
let b:match_skip = 's:comment\|string\|character\|special'
let b:undo_ftplugin ..= " | unlet! b:match_skip b:match_words"
endif
updated for version 7.2a
2008-06-24 21:56:24 +00:00
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
" Win32 and GTK can filter files in the browse dialog
Updated runtime files.
2012-07-12 22:01:11 +02:00
if (has("gui_win32") || has("gui_gtk")) && !exists("b:browsefilter")
updated for version 7.0001
2004-06-13 20:20:40 +00:00
if &ft == "cpp"
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 = "C++ Source Files (*.cpp, *.c++)\t*.cpp;*.c++\n" ..
\ "C Header Files (*.h)\t*.h\n" ..
\ "C Source Files (*.c)\t*.c\n"
updated for version 7.0014
2004-09-02 19:12:26 +00:00
elseif &ft == "ch"
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 = "Ch Source Files (*.ch, *.chf)\t*.ch;*.chf\n" ..
\ "C Header Files (*.h)\t*.h\n" ..
\ "C Source Files (*.c)\t*.c\n"
updated for version 7.0001
2004-06-13 20:20:40 +00:00
else
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 = "C Source Files (*.c)\t*.c\n" ..
\ "C Header Files (*.h)\t*.h\n" ..
\ "Ch Source Files (*.ch, *.chf)\t*.ch;*.chf\n" ..
\ "C++ Source Files (*.cpp, *.c++)\t*.cpp;*.c++\n"
endif
if has("win32")
let b:browsefilter ..= "All Files (*.*)\t*\n"
else
let b:browsefilter ..= "All Files (*)\t*\n"
updated for version 7.0001
2004-06-13 20:20:40 +00:00
endif
Update runtime files
2021-09-21 20:09:51 +02:00
let b:undo_ftplugin ..= " | unlet! b:browsefilter"
updated for version 7.0001
2004-06-13 20:20:40 +00:00
endif
updated for version 7.0090
2005-06-22 22:35:10 +00:00
let &cpo = s:cpo_save
unlet s:cpo_save
Copy Permalink