vim/vim-autoformat
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
2ed8f00bb5
vim-autoformat/plugin/defaults.vim

81 lines
4.1 KiB
VimL
Raw Normal View History

Try all available formatters until one works
2015-05-23 04:02:05 -04:00
let g:format_def_autopep8 = '"autopep8 - ".(&textwidth ? "--max-line-length=".&textwidth : "")'
let g:format_def_test = '"asdf"'
let g:format_def_another_autopep8 = '"autopep8 - --indent-size 2 ".(&textwidth ? "--max-line-length=".&textwidth : "")'
if !exists("g:formatters_python")
let g:formatters_python = [
\ 'test',
\ 'another_autopep8',
\ 'autopep8',
\ ]
endif
check for user config before setting defaults
2013-03-09 05:52:11 -05:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatters_cs")
"let g:formatters_cs = ['"astyle --mode=cs --style=ansi --indent-namespaces -pcH".(&expandtab ? "s".&shiftwidth : "t")']
"endif
check for user config before setting defaults
2013-03-09 05:52:11 -05:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatters_c")
"let g:formatters_c = ['"astyle --mode=c --style=ansi -pcH".(&expandtab ? "s".&shiftwidth : "t")']
"endif
check for user config before setting defaults
2013-03-09 05:52:11 -05:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatprg_cpp") | let g:formatprg_cpp = "astyle" | endif
"if !exists("g:formatprg_args_expr_cpp") && !exists("g:formatprg_args_cpp")
"let g:formatprg_args_expr_cpp = '"--mode=c --style=ansi -pcH".(&expandtab ? "s".&shiftwidth : "t")'
"endif
Fix #34: Add Objective-C Support
2015-01-08 04:48:38 -05:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatprg_objc") | let g:formatprg_objc = "clang-format" | endif
"if !exists("g:formatprg_args_expr_objc") && !exists("g:formatprg_args_objc")
"let g:formatprg_args_expr_objc = '"-style=\"{BasedOnStyle: WebKit, AlignTrailingComments: true, ".(&textwidth ? "ColumnLimit: ".&textwidth.", " : "").(&expandtab ? "UseTab: Never, IndentWidth: ".&shiftwidth : "UseTab: Always")."}\""'
"endif
check for user config before setting defaults
2013-03-09 05:52:11 -05:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatprg_java") | let g:formatprg_java = "astyle" | endif
"if !exists("g:formatprg_args_expr_java") && !exists("g:formatprg_args_java")
"let g:formatprg_args_expr_java = '"--mode=java --style=ansi -pcH".(&expandtab ? "s".&shiftwidth : "t")'
"endif
check for user config before setting defaults
2013-03-09 05:52:11 -05:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatprg_xml") | let g:formatprg_xml = "tidy" | endif
"if !exists("g:formatprg_args_expr_xml") && !exists("g:formatprg_args_xml")
"let g:formatprg_args_expr_xml = '"-q -xml --show-errors 0 --show-warnings 0 --force-output --indent auto --indent-spaces ".&shiftwidth." --vertical-space yes --tidy-mark no -wrap ".&textwidth'
"endif
Readme update, samples added, bugifx defaults
2013-03-16 07:21:55 -04:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatprg_xhtml") | let g:formatprg_xhtml = "tidy" | endif
"if !exists("g:formatprg_args_expr_xhtml") && !exists("g:formatprg_args_xhtml")
"let g:formatprg_args_expr_xhtml = '"-q --show-errors 0 --show-warnings 0 --force-output --indent auto --indent-spaces ".&shiftwidth." --vertical-space yes --tidy-mark no -asxhtml -wrap ".&textwidth'
"endif
check for user config before setting defaults
2013-03-09 05:52:11 -05:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatprg_css") | let g:formatprg_css = "css-beautify" | endif
"if !exists("g:formatprg_args_expr_css") && !exists("g:formatprg_args_css")
"let g:formatprg_args_expr_css = '"-f - -s ".&shiftwidth'
"endif
add CSS formatting (using `css-beautify`) to defaults
2014-05-30 16:42:30 -04:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatprg_scss") | let g:formatprg_scss = "sass-convert" | endif
"if !exists("g:formatprg_args_expr_scss") && !exists("g:formatprg_args_scss")
"let g:formatprg_args_expr_scss = '"-F scss -T scss --indent " . (&expandtab ? &shiftwidth : "t")'
"endif
Add SCSS formatting using sass-convert
2014-09-26 13:29:06 -04:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatprg_html") | let g:formatprg_html = "html-beautify" | endif
"if !exists("g:formatprg_args_expr_html") && !exists("g:formatprg_args_html")
"let g:formatprg_args_expr_html = '"-f - -s ".&shiftwidth'
"endif
Fix #13 and some cleanup.
2013-12-20 14:34:38 -05:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatprg_javascript") | let g:formatprg_javascript = "js-beautify" | endif
"if !exists("g:formatprg_args_expr_javascript") && !exists("g:formatprg_args_javascript")
"let g:formatprg_args_expr_javascript = '"-f - -".(&expandtab ? "s ".&shiftwidth : "t").(&textwidth ? " -w ".&textwidth : "")'
"endif
Add JSON formatting using js-beautify
2014-06-29 15:15:10 -04:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatprg_typescript") | let g:formatprg_typescript = "tsfmt" | endif
"if !exists("g:formatprg_args_expr_typescript") && !exists("g:formatprg_args_typescript")
"let g:formatprg_args_expr_typescript = '"--stdin %"'
"endif
Added TypeScript formatting options vvakame/typescript-formatter now support reading from stdin, but a filename has to be specified. I've tried it with both unsaved and saved buffers and it works fine.
2015-03-22 11:59:57 -04:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatprg_json") | let g:formatprg_json = "js-beautify" | endif
"if !exists("g:formatprg_args_expr_json") && !exists("g:formatprg_args_json")
"let g:formatprg_args_expr_json = '"-f - -".(&expandtab ? "s ".&shiftwidth : "t")'
"endif
rbeautify as a beautifier for ruby
2014-12-09 05:17:30 -05:00
Multiple formatters. Don't write errors to buffer. Using python we can check for formatter errors instead of writing the errors to the buffer. Multiple formatters can be supplied by lists now. Backward compatibility breaks: - Variable names have changed - Formatter is specified as one expression - gq has been removed, Autoformat should accept ranges - python has to be compiled in To be done: - Find easy way to selected default formatter out of available formatter - Make autoformat accept ranges
2015-05-18 13:27:00 -04:00
"if !exists("g:formatprg_ruby") | let g:formatprg_ruby = "rbeautify" | endif
"if !exists("g:formatprg_args_expr_ruby") && !exists("g:formatprg_args_ruby")
"let g:formatprg_args_expr_ruby = '(&expandtab ? "-s -c ".&shiftwidth : "-t")'
"endif
Reference in New Issue Copy Permalink