R. Steve McKown [Mon, 18 Jan 2016 23:39:15 +0000 (16:39 -0700)]
vimrc: update for newest vim-mkbuild plugin
The vim-mkbuild plugin has been improved. It supports two diferent file
search sources for Unite!
* <leader>E maps to unite using the mkbuild/file source, which provides
all files in the project, including other projects referenced
externally in the optional extrefs file.
* <leader>e maps to unite using the mkbuild/file_xref source, which
provides that subset of files used in a specific mkbuild build. This
version requires the use of <leader>x first to set a build. If no
build is available, mkbuild/file_xref instead works just like
mkbuild/file.
R. Steve McKown [Mon, 18 Jan 2016 18:11:56 +0000 (11:11 -0700)]
vim: remove vimproc.vim plugin
Not using anything right now that requires vimproc. Unite! can make use
of it in its async modes, but currently there appears no need for these
async modes, and they in fact seem to cause some issues.
R. Steve McKown [Mon, 18 Jan 2016 07:05:28 +0000 (00:05 -0700)]
vim: change wildmode
Change wildmode so that one can 'back up' with S-Tab to the original
text entered before pressing Tab to activate wildmode. This prevents
the need from needing to hit backspace a bunch of times to add more
correct characters before pressing Tab again to get a shorter list.
R. Steve McKown [Mon, 18 Jan 2016 05:35:11 +0000 (22:35 -0700)]
bashrc: support autojump
Autojump rocks. The prompt command is extended to maintain an MRU of
directories, so that one can use 'j fragment' to jump to a directory
with 'fragment' in its name. This should be a nice efficiency win.
R. Steve McKown [Mon, 18 Jan 2016 04:49:31 +0000 (21:49 -0700)]
vim: change unite mappings
* Start quicklist search in insert mode. Interactive filtering is
probably the reason Unite! search of quickfix is better than normal
quickfix functionality.
* Ditch dynamicbottom property for Unite! searching of command and
search histories. Make all the Unite! search behaviors more
consistent across usages.
R. Steve McKown [Mon, 18 Jan 2016 00:23:18 +0000 (17:23 -0700)]
vim: <Leader>e uses unite mkbfiles
By using the latest unite integration as part of the vim-mkbuild plugin,
dmenu is no longer required. Don't get me wrong -- dmenu is a stellar
tool and I use it for many purposes on my desktop configuration.
However, I'd prefer for my vim configuration to be less dependent on
desktop features. Also, since I'm using unite in several other ways,
moving the method to select project source files to unite provides
greater consistency.
R. Steve McKown [Mon, 18 Jan 2016 00:19:41 +0000 (17:19 -0700)]
vim: update vim-mkbuild, obsoletes unite-xrefs
* unite-xrefs has been folded into vim-mkbuild and the former is no
longer required.
* vim-mkbuild unite integration adds file search similar to
mkbuild#DmenuOpen(). The unite source is 'mkbuild'
R. Steve McKown [Sun, 17 Jan 2016 19:12:00 +0000 (12:12 -0700)]
vim: update bindings for command and search history
Shorten command history search via Unite! to <Leader>:, similar to the
normal command buffer access via q:. Similarly, <Leader>/ to search
search history via Unite!. Don't override the vim standard mappings of
q: and q/.
R. Steve McKown [Thu, 24 Dec 2015 14:30:53 +0000 (07:30 -0700)]
vim: leak no info for files opened on /run/shm
password-store opens encrypted files for edit unencrypted in /run/shm.
This autocmd turns off vim features which cause leakage of that
unencrypted information.
R. Steve McKown [Fri, 30 Oct 2015 20:36:27 +0000 (14:36 -0600)]
Xresources: support CLIPBOARD paste
Middle mouse up event pastes from the PRIMARY buffer. Define Shift plus
middle mouse up event to paste from the CLIPBOARD. PRIMARY is the most
recently highlighted text, where CLIPBOARD is generally populated with a
cut or copy command from a graphical application.
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.