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

70 lines
2.4 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 "
" "
" Maintainer: Prurigro (prurigro-at-gmail-dot-com) "
" 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
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
"DARKCLOUD VIM CONFIG FOLDER PATH: {{{
" 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:
"
" let g:darkcloudpath="/etc/darkcloud-vimconfig"
if filereadable(glob("~/.vim/darkcloud-path.vim"))
source ~/.vim/darkcloud-path.vim
else
let g:darkcloudpath="/etc/darkcloud-vimconfig"
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
"USER CONFIG SETTINGS: {{{
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 vim/vimrc.user doesn't already exist, run the 'update' script to have
" it created, then toggle these settings there to override these and no
" avoid conflicting with updates.
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
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
"Filer File Manager On Empty Buffers: (1:empty buffer loads filer | 0:buffer remains empty)
let g:autostartfiler=1
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
"Syntax Checking Autostart: (1:start toggled on | 0: start toggled off)
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
let g:autostartchecker=1
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
"Vim Starts With The Tagbar Open: (1:start open | 0:start closed)
after living with it autoenabled for a little while, I've decided that the tagbar is better off defaulting to on-demand.
2014-04-08 05:23:42 -04:00
let g:autostarttagbar=0
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
"Powerline Font Support: (1:enabled | 0:disabled)
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
let g:powerlinefonts=0
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
"GVim Font Selection: (term font set by terminal)
set guifont=Droid\ Sans\ Mono\ 12
"}}}
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 DARKCLOUD CONFIG AND THEME FILES: {{{
"Add Config Directory: (distro-agnostic system-wide)
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
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
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
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 Plugins:
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
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 Colour Scheme:
colorscheme darkcloud
"}}}
Reference in a new issue Copy permalink