R. Steve McKown [Wed, 9 Sep 2015 23:03:13 +0000 (17:03 -0600)]
vim/vimrc: change cinoptions
Previously, cinoptions attempted to use 1 shiftwidth for line
continuations except for if/while/switch and related lines, where two
sw's were used. However, looking at code in the various libraries, it
appears that more commonly the line continuation is 2 sw's in all cases.
R. Steve McKown [Fri, 19 Jun 2015 15:32:06 +0000 (09:32 -0600)]
vim: add mappings for vim-mkbuild
Use <leader>e to map to mkbuild#DmenuOpen('e'). Remove other
conflicting <leader>e mappings:
* <leader>e[x] mappings for various open methods. I generally just use
the '-' mapping to netrw. Although open in a new split might be
handy, I've never used it so far.
* <leader>e mapping for EasyMotion. There isn't that much value in
* <leader>e when <leader>w is available.
R. Steve McKown [Sun, 14 Jun 2015 06:37:07 +0000 (00:37 -0600)]
dwmrc: re-merge ~/.Xresources
To work around a lightdm bug (it merges with -nocpp), re-merge here so
that our #defines work. There is an outstanding launchpad bug on this
issue: #1244578. It may not be 'fixed'.
R. Steve McKown [Wed, 10 Jun 2015 15:35:49 +0000 (09:35 -0600)]
Better text file handling
1. Turn on formatoptions 't' for text files
2. The text filetype doesn't work in some cases. Add specific commands
for files like README.
3. Map 'coa' to toggling of the formatoptions 'a', auto-format
paragraphs.
4. Previous 'coa' -> 'cop', for toggling auto pairing (delimitMate).
5. Previous 'cop' -> 'co(', for toggling rainbow parenthesis. This is a
feature I've not used much, so maybe it needs to go away.
I'm debating the value of formatoptions 'n' for certain files. It could
be helpful for some things but seems to break others. For now it is not
being used.
With 'coa' present, there is some merit to considering adding 'a' by
default for text files, since it would then be trivial to turn off. But
since 'a' autoformats paragraphs all the time, any 'hand' formatting
will be lost with the next key press in that paragraph. So it's
probably better to leave it as a selectively enabled element as it is
now.
R. Steve McKown [Mon, 8 Jun 2015 21:14:15 +0000 (15:14 -0600)]
Relocate vim swap/backup/undo files
The location where swap/backup/undo files should be in a subdirectory of
a vim runtimepath, and one that is user specific. The idea of using
something like the previous .local/shared/vim is too linux distro
specific.
Since MacVim and *nix vim both have $HOME/.vim in the runtimepath, then
this is the best place. For Windows, we have to use $HOME/vimfiles
instead.
R. Steve McKown [Mon, 8 Jun 2015 21:04:04 +0000 (15:04 -0600)]
No need to link ~/.vimrc
Because VIM 7.4 (and maybe earlier) looks for the .vimrc file in
$HOME/.vimrc and $HOME/vim/.vimrc on Linux, there is no need to make a
separate link for .vimrc if vimrc is in vim/.
R. Steve McKown [Mon, 8 Jun 2015 20:26:31 +0000 (14:26 -0600)]
pathogen#infect(): don't list default parameter
'bundle/{}' is the default, so there is no need to list it. When
migrating the vim configuration into the dotfiles repository, I at one
point encountered errors when using pathogen#infect() without an
argument, where listing the default argument worked. I didn't at that
time investigate the problem, which appears to be no problem.
R. Steve McKown [Mon, 8 Jun 2015 19:42:10 +0000 (13:42 -0600)]
Swap/undo/backup is working again
Not sure, but sometime after the end of April the whole swap/undo/backup
stuff quit working. It's almost as if a system configuration file
changed, but I don't know what. In any case, the changes here to vimrc
(~/.vimrc) gets things working even better:
* If the directory structure used for these files, at
~/.local/share/vim, are not present, they are created.
* If backups can be written, only the preferred location is made
available.
* If undo files can be written, only the preferred location is made
available.
R. Steve McKown [Fri, 5 Jun 2015 22:20:08 +0000 (16:20 -0600)]
Try lucius light for xterm and vim
Set up lucius light colors in both xterm and vim. This way both look
the same -- this is aesthetically pleasing. Lucius has a nice low
contrast, but with a light background, the transition from terminals to
web browser isn't as hard on the eyes.
Ideally the lucius scheme could be modified slightly to work with an
even lighter/whiter background to get closer to others, but let's try
this for now.
R. Steve McKown [Fri, 5 Jun 2015 20:24:49 +0000 (14:24 -0600)]
Try PaperColors vim color theme
Not bad, but the background is different than xterms. I think ideally
they would be nearly the same. This really suggests that I want an 8
color scheme? Like a light miro8.
R. Steve McKown [Fri, 5 Jun 2015 20:13:56 +0000 (14:13 -0600)]
Return to light background
The dark backgrounds look great, but too many programs I use force a
white background, such as the web pages, thunderbird, and so on.
Switching between dark background and light background is quite jarring.
It may be better to find and use decent light background setups for
xterm/vim and ensure the monitor brightness is set appropriately low.
R. Steve McKown [Fri, 5 Jun 2015 19:15:38 +0000 (13:15 -0600)]
Try dark color scheme
From information at http://jasonwryan.com.
* New xterm colors in .Xresources
* Use jellybeans color scheme
Jason created his own colorschemes which line up nicely with the xterm
colors provided. However as of right now they do not work in gvim. And
I think I like jellybeans better.
http://bytefluent.com/vivify/ is a great reference for vim colorschemes.
R. Steve McKown [Tue, 2 Jun 2015 23:02:37 +0000 (17:02 -0600)]
Initial commit
This commit contains all the information from the repository at
repo.titaniummirror.com:smckown/vim-config.git. This repository will
eventually replace that one. This repository will contain all
'dotfiles' that are worth saving and also cloning to different machines.