kevin/darkcloud-nvimconfig
1
0
Fork 0
mirror of https://github.com/prurigro/darkcloud-nvimconfig.git synced 2024-11-22 03:34:10 -05:00
Code Issues Projects Releases Packages Wiki Activity
darkcloud-nvimconfig/vimrc

125 lines
4.5 KiB
VimL
Raw Normal View History

Added more complete and descriptive headers to the config files, including the URL the config can be downloaded. Added a new variable that determines whether the filer will autostart on empty buffers or not. Set powerline fonts not to load by default. Changed the order to load the config files so the user config settings are applied to plugins.
2014-04-09 08:07:12 -04:00
"============================================================"
" "
" Darkcloud Vim Config: vimrc "
" "
Added commandline argument support to the update script that includes options to display help and version information, as well as to disable colour output (with both English and American spellings of colour). Some minor changes to wording/style were also made in the title blocks and README.
2014-06-17 01:49:46 -04:00
" By: Kevin MacMartin (prurigro@gmail.com) "
Added more complete and descriptive headers to the config files, including the URL the config can be downloaded. Added a new variable that determines whether the filer will autostart on empty buffers or not. Set powerline fonts not to load by default. Changed the order to load the config files so the user config settings are applied to plugins.
2014-04-09 08:07:12 -04:00
" Website: https://github.com/prurigro/darkcloud-vimconfig "
" "
" License: MIT "
" "
"============================================================"
Initial commit with a relatively well configured package (config, theme and plugins), and a README to explain the details
2014-02-20 23:24:20 -05:00
Load the colorscheme before the config files
2014-07-25 23:50:05 -04:00
"darkcloud vim config folder path: {{{
Normalize comment style a bit
2018-03-14 11:38:51 -04:00
"if you want to use darkcloud-vimconfig as a package without symlinking
"the vim folder or placing it @ /etc/darkcloud-vimconfig, create a file
"@ ~/.vim/darkcloud-path.vim and in it place the following, except with
"the path pointing to the cloned repo:
Tweaked the update script to drop the user variables from vimrc into vimrc.user when it's created. a new user-based config file can be used to specify the location of the project folder without altering vimrc, if it's a symlink and bound to bump into conflicts as changes are made. The README was updated to reflect a few of the recent changes. The tagbar now outputs to the lightline statusline if there's anything to report. A new variable was added to choose whether to always start with the tagbar enabled if the format is compatible, or use the older behaviour, where it would only appear when triggered. The default is to enable it 24/7.
2014-04-08 03:39:10 -04:00
"
Normalize comment style a bit
2018-03-14 11:38:51 -04:00
"let g:darkcloudpath = "/etc/darkcloud-vimconfig"
Tweaked the update script to drop the user variables from vimrc into vimrc.user when it's created. a new user-based config file can be used to specify the location of the project folder without altering vimrc, if it's a symlink and bound to bump into conflicts as changes are made. The README was updated to reflect a few of the recent changes. The tagbar now outputs to the lightline statusline if there's anything to report. A new variable was added to choose whether to always start with the tagbar enabled if the format is compatible, or use the older behaviour, where it would only appear when triggered. The default is to enable it 24/7.
2014-04-08 03:39:10 -04:00
if filereadable(glob("~/.vim/darkcloud-path.vim"))
source ~/.vim/darkcloud-path.vim
else
Clean up formatting in the vimrc and vimpagerrc
2018-03-11 23:37:17 -04:00
let g:darkcloudpath = "/etc/darkcloud-vimconfig"
Tweaked the update script to drop the user variables from vimrc into vimrc.user when it's created. a new user-based config file can be used to specify the location of the project folder without altering vimrc, if it's a symlink and bound to bump into conflicts as changes are made. The README was updated to reflect a few of the recent changes. The tagbar now outputs to the lightline statusline if there's anything to report. A new variable was added to choose whether to always start with the tagbar enabled if the format is compatible, or use the older behaviour, where it would only appear when triggered. The default is to enable it 24/7.
2014-04-08 03:39:10 -04:00
endif
"}}}
Tons of changes all in one commit because I'd broken a commit a while back and opted to simply reverse them all- Lots of colour changes, the update script now removes decommissioned bundles, gentags script can now have additional paths added to it when generating a tags file, README is much improved, fixed a few issues that required remapping some toggles, fixed a bunch of issues with the colourscheme between the terminal and gvim. You can now setup a custom config file to have loaded after the darkcloud-vimconfig ones, and there's a custom location for pathogen modules too, to make things tidier without necessarily needing to use an additional runtimepath. You can also create a file in your home directory to assign filetypes to programs, for use with the file manager. A file can be placed in ~/.vim/ with file associations and prorams to launch them with. The file manager will also open a file with vim by hitting shift+enter, since e isn't all that comfortablly placed. The vimrc can now also point to the darkcloud-vimconfig folder, rather than relying on the vim folder being in a specific location, and the after folder is now configured to work in the project too.
2014-04-04 19:49:02 -04:00
"LOAD DARKCLOUD CONFIG AND THEME FILES: {{{
"Add Config Directory: (distro-agnostic system-wide)
Clean up formatting in the vimrc and vimpagerrc
2018-03-11 23:37:17 -04:00
let &runtimepath = printf('%s,%s/vim,%s/vim/after',&runtimepath,g:darkcloudpath,g:darkcloudpath)
Tweaked the theme and syntax definitions a bit more. Configured the file manager's theme, settings and keyboard mappings. Played around with the keyboard mappings in general quite a bit more. All the toggles output what they're doing now, though not their actual status in most cases at this point, and only in normal mode. The bottom scrollbar is now part of the gui scrollbar toggle as it turned out it can be auto-disabled when the content isn't wide enough anyway. I realized a bad hack to get visual paste ontop to work without replacing the paste buffer with whatever it was pasting over meant that pasting at the start and end of the line would leave issues with spacing, so I found a plugin that fixed the problem the right way and hooked things up through that.. Whether syntax checking is enabled by default or needs to be toggled on can now be set in the vimrc. Some small bugfixes and improvements were also made.
2014-04-03 06:17:16 -04:00
Rebuild the theme so all the colors are declared and imported, to make it easier to update, and use conditionals when declaring the colors rather than trying to compute equivalent hex codes
2023-05-30 00:41:59 -04:00
"Load Colours
Don't apply the colorscheme in a vterm
2023-08-17 16:17:46 -04:00
if &term != "linux"
runtime colors/palette.vim
Rebuild the theme so all the colors are declared and imported, to make it easier to update, and use conditionals when declaring the colors rather than trying to compute equivalent hex codes
2023-05-30 00:41:59 -04:00
Don't apply the colorscheme in a vterm
2023-08-17 16:17:46 -04:00
"Load Colour Scheme:
colorscheme default "hack to fix vimrc colorschemes in some versions of vim
colorscheme darkcloud
endif
Load the colorscheme before the config files
2014-07-25 23:50:05 -04:00
Tons of changes all in one commit because I'd broken a commit a while back and opted to simply reverse them all- Lots of colour changes, the update script now removes decommissioned bundles, gentags script can now have additional paths added to it when generating a tags file, README is much improved, fixed a few issues that required remapping some toggles, fixed a bunch of issues with the colourscheme between the terminal and gvim. You can now setup a custom config file to have loaded after the darkcloud-vimconfig ones, and there's a custom location for pathogen modules too, to make things tidier without necessarily needing to use an additional runtimepath. You can also create a file in your home directory to assign filetypes to programs, for use with the file manager. A file can be placed in ~/.vim/ with file associations and prorams to launch them with. The file manager will also open a file with vim by hitting shift+enter, since e isn't all that comfortablly placed. The vimrc can now also point to the darkcloud-vimconfig folder, rather than relying on the vim folder being in a specific location, and the after folder is now configured to work in the project too.
2014-04-04 19:49:02 -04:00
"Load Settings:
runtime config/settings.vim
Initial commit with a relatively well configured package (config, theme and plugins), and a README to explain the details
2014-02-20 23:24:20 -05:00
Replace neocomplete with deoplete
2018-03-13 15:38:03 -04:00
"Initialize Plugins:
Make pathogen_disabled global so it can be checked later, and allow it to be overridden prior to loading so an external vimrc can disable plugins before its loaded
2024-02-23 16:13:01 -05:00
let g:pathogen_disabled = get(g:, "pathogen_disabled", [])
Disable plugins that complain about missing dependencies when those dependencies aren't available
2017-02-12 18:55:17 -05:00
Replace neocomplete with deoplete
2018-03-13 15:38:03 -04:00
if has('python3')
Move python to optional dependencies since the vimrc is smart enough to disable those plugins when they aren't being used, add the msgpack requirement for deoplete, and don't load deoplete if msgpack isn't available
2020-02-28 00:16:49 -05:00
"configure pythonx and check for the python-neovim and python-msgpack libraries if python3 is found
Fix the deoplete detection for neovim
2018-03-15 13:55:29 -04:00
if !has('nvim')
set pyxversion=3
endif
Replace neocomplete with deoplete
2018-03-13 15:38:03 -04:00
Move python to optional dependencies since the vimrc is smart enough to disable those plugins when they aren't being used, add the msgpack requirement for deoplete, and don't load deoplete if msgpack isn't available
2020-02-28 00:16:49 -05:00
"check for python-neovim
Replace neocomplete with deoplete
2018-03-13 15:38:03 -04:00
redir => python_neovim_check
Fix the deoplete detection for neovim
2018-03-15 13:55:29 -04:00
silent python3 exec("import pkgutil\nneovim = pkgutil.find_loader('neovim')\nfound = neovim is not None\nprint(found)")
Replace neocomplete with deoplete
2018-03-13 15:38:03 -04:00
redir END
if substitute(python_neovim_check, '^\n*\([^\n]*\)\n*$', '\1', '') == 'True'
let g:python_neovim = 1
else
let g:python_neovim = 0
endif
Move python to optional dependencies since the vimrc is smart enough to disable those plugins when they aren't being used, add the msgpack requirement for deoplete, and don't load deoplete if msgpack isn't available
2020-02-28 00:16:49 -05:00
"check for python-msgpack
redir => python_msgpack_check
silent python3 exec("import pkgutil\nmsgpack = pkgutil.find_loader('msgpack')\nfound = msgpack is not None\nprint(found)")
redir END
Re-add neovim fixkey disable
2018-03-12 10:56:36 -04:00
Move python to optional dependencies since the vimrc is smart enough to disable those plugins when they aren't being used, add the msgpack requirement for deoplete, and don't load deoplete if msgpack isn't available
2020-02-28 00:16:49 -05:00
if substitute(python_msgpack_check, '^\n*\([^\n]*\)\n*$', '\1', '') == 'True'
let g:python_msgpack = 1
else
let g:python_msgpack = 0
endif
else
"if python isn't available disable plugins that depend on it and set library variables to false
Make pathogen_disabled global so it can be checked later, and allow it to be overridden prior to loading so an external vimrc can disable plugins before its loaded
2024-02-23 16:13:01 -05:00
call add(g:pathogen_disabled, 'MatchTagAlways')
Move python to optional dependencies since the vimrc is smart enough to disable those plugins when they aren't being used, add the msgpack requirement for deoplete, and don't load deoplete if msgpack isn't available
2020-02-28 00:16:49 -05:00
let g:python_neovim = 0
let g:python_msgpack = 0
Disable plugins that complain about missing dependencies when those dependencies aren't available
2017-02-12 18:55:17 -05:00
endif
Don't add neocomplete.vim to pathogen_disabled twice if neovim is being used as well as having lua support disabled, and don't include neocomplete keyboard settings if it's disabled because of missing lua support
2017-02-12 19:08:28 -05:00
Don't load gutentags if ctags can't be found
2022-04-23 23:44:37 -04:00
"don't load vim-gutentags if ctags can't be found
if !executable('ctags')
Make pathogen_disabled global so it can be checked later, and allow it to be overridden prior to loading so an external vimrc can disable plugins before its loaded
2024-02-23 16:13:01 -05:00
call add(g:pathogen_disabled, 'vim-gutentags')
Don't load gutentags if ctags can't be found
2022-04-23 23:44:37 -04:00
endif
Move python to optional dependencies since the vimrc is smart enough to disable those plugins when they aren't being used, add the msgpack requirement for deoplete, and don't load deoplete if msgpack isn't available
2020-02-28 00:16:49 -05:00
if !g:python_neovim || !g:python_msgpack
"don't load deoplete if either of its python dependencies are missing
Make pathogen_disabled global so it can be checked later, and allow it to be overridden prior to loading so an external vimrc can disable plugins before its loaded
2024-02-23 16:13:01 -05:00
call add(g:pathogen_disabled, 'deoplete.nvim')
call add(g:pathogen_disabled, 'neco-syntax')
call add(g:pathogen_disabled, 'nvim-yarp')
call add(g:pathogen_disabled, 'vim-hug-neovim-rpc')
Replace neocomplete with deoplete
2018-03-13 15:38:03 -04:00
elseif has('nvim')
Move python to optional dependencies since the vimrc is smart enough to disable those plugins when they aren't being used, add the msgpack requirement for deoplete, and don't load deoplete if msgpack isn't available
2020-02-28 00:16:49 -05:00
"don't load the neovim compatibility plugins required by deoplete if actually running neovim
Make pathogen_disabled global so it can be checked later, and allow it to be overridden prior to loading so an external vimrc can disable plugins before its loaded
2024-02-23 16:13:01 -05:00
call add(g:pathogen_disabled, 'nvim-yarp')
call add(g:pathogen_disabled, 'vim-hug-neovim-rpc')
Disable neocomplete if vim doesn't have lua
2018-03-13 11:49:47 -04:00
endif
Disable autocompletion logic when running in vimpager mode
2023-02-06 15:52:28 -05:00
"disable autocompletion logic when running in vimpager mode
if exists('g:vimpager.enabled')
Make pathogen_disabled global so it can be checked later, and allow it to be overridden prior to loading so an external vimrc can disable plugins before its loaded
2024-02-23 16:13:01 -05:00
call add(g:pathogen_disabled, 'deoplete.nvim')
call add(g:pathogen_disabled, 'neco-syntax')
call add(g:pathogen_disabled, 'nvim-yarp')
call add(g:pathogen_disabled, 'vim-hug-neovim-rpc')
Disable autocompletion logic when running in vimpager mode
2023-02-06 15:52:28 -05:00
endif
Move python to optional dependencies since the vimrc is smart enough to disable those plugins when they aren't being used, add the msgpack requirement for deoplete, and don't load deoplete if msgpack isn't available
2020-02-28 00:16:49 -05:00
"if neovim is being used we should disable plugins that aren't compatible or necessary
if has('nvim')
Make pathogen_disabled global so it can be checked later, and allow it to be overridden prior to loading so an external vimrc can disable plugins before its loaded
2024-02-23 16:13:01 -05:00
call add(g:pathogen_disabled, 'vim-fixkey')
Move python to optional dependencies since the vimrc is smart enough to disable those plugins when they aren't being used, add the msgpack requirement for deoplete, and don't load deoplete if msgpack isn't available
2020-02-28 00:16:49 -05:00
endif
Normalize comment style a bit
2018-03-14 11:38:51 -04:00
"use pathogen to load plugins that haven't been disabled
Tons of changes all in one commit because I'd broken a commit a while back and opted to simply reverse them all- Lots of colour changes, the update script now removes decommissioned bundles, gentags script can now have additional paths added to it when generating a tags file, README is much improved, fixed a few issues that required remapping some toggles, fixed a bunch of issues with the colourscheme between the terminal and gvim. You can now setup a custom config file to have loaded after the darkcloud-vimconfig ones, and there's a custom location for pathogen modules too, to make things tidier without necessarily needing to use an additional runtimepath. You can also create a file in your home directory to assign filetypes to programs, for use with the file manager. A file can be placed in ~/.vim/ with file associations and prorams to launch them with. The file manager will also open a file with vim by hitting shift+enter, since e isn't all that comfortablly placed. The vimrc can now also point to the darkcloud-vimconfig folder, rather than relying on the vim folder being in a specific location, and the after folder is now configured to work in the project too.
2014-04-04 19:49:02 -04:00
runtime bundle/vim-pathogen/autoload/pathogen.vim
Initial commit with a relatively well configured package (config, theme and plugins), and a README to explain the details
2014-02-20 23:24:20 -05:00
Tons of changes all in one commit because I'd broken a commit a while back and opted to simply reverse them all- Lots of colour changes, the update script now removes decommissioned bundles, gentags script can now have additional paths added to it when generating a tags file, README is much improved, fixed a few issues that required remapping some toggles, fixed a bunch of issues with the colourscheme between the terminal and gvim. You can now setup a custom config file to have loaded after the darkcloud-vimconfig ones, and there's a custom location for pathogen modules too, to make things tidier without necessarily needing to use an additional runtimepath. You can also create a file in your home directory to assign filetypes to programs, for use with the file manager. A file can be placed in ~/.vim/ with file associations and prorams to launch them with. The file manager will also open a file with vim by hitting shift+enter, since e isn't all that comfortablly placed. The vimrc can now also point to the darkcloud-vimconfig folder, rather than relying on the vim folder being in a specific location, and the after folder is now configured to work in the project too.
2014-04-04 19:49:02 -04:00
"Load Keymappings:
runtime config/keyboard.vim
Initial commit with a relatively well configured package (config, theme and plugins), and a README to explain the details
2014-02-20 23:24:20 -05:00
Added more complete and descriptive headers to the config files, including the URL the config can be downloaded. Added a new variable that determines whether the filer will autostart on empty buffers or not. Set powerline fonts not to load by default. Changed the order to load the config files so the user config settings are applied to plugins.
2014-04-09 08:07:12 -04:00
"Load User Config:
runtime vimrc.user
"Load Plugin Configuration:
runtime config/plugins.vim
Load after.vim after plugins.vim
2014-07-16 07:34:35 -04:00
"Load After Config:
runtime config/after.vim
Tons of changes all in one commit because I'd broken a commit a while back and opted to simply reverse them all- Lots of colour changes, the update script now removes decommissioned bundles, gentags script can now have additional paths added to it when generating a tags file, README is much improved, fixed a few issues that required remapping some toggles, fixed a bunch of issues with the colourscheme between the terminal and gvim. You can now setup a custom config file to have loaded after the darkcloud-vimconfig ones, and there's a custom location for pathogen modules too, to make things tidier without necessarily needing to use an additional runtimepath. You can also create a file in your home directory to assign filetypes to programs, for use with the file manager. A file can be placed in ~/.vim/ with file associations and prorams to launch them with. The file manager will also open a file with vim by hitting shift+enter, since e isn't all that comfortablly placed. The vimrc can now also point to the darkcloud-vimconfig folder, rather than relying on the vim folder being in a specific location, and the after folder is now configured to work in the project too.
2014-04-04 19:49:02 -04:00
"}}}
Reference in a new issue Copy permalink