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.
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.
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.
