Tony Duckles [Thu, 19 Jul 2018 02:47:19 +0000 (21:47 -0500)]
.bashrc: Use `paste ... -` when reading from pipe
GNU versions of `paste` will read from STDIN when no explicit file
arguments, but some other UNIX platforms [e.g. AIX] have versions of
`paste` which required an explicit "-" filename argument to indicate
"read from STDIN".
Build discrete "start" and "end" lists, and prepend/append those lists
to $PATH/$MANPATH once at the end. This makes it easier to control the
discrete order of paths in the prefix vs suffix sections. For example,
I always want $HOME/bin to be at the very-start of $PATH so that I can
put an "override" script in $HOME/bin and that can always win over
"normal" binaries in other later directories in $PATH.
Tony Duckles [Sat, 17 Feb 2018 18:29:48 +0000 (12:29 -0600)]
.gitconfig: Use `diff-highlight` contrib script as diff-filter
- bin/diff-filter: Wrapper around calling the Git `diff-highlight`
contrib script. This will degrade gracefully if `diff-highlight`
script cannot be found in standard locations.
- bin/diff-pager: Wrapper around calling new `diff-filter | $PAGER`.
This can be used via `git config core.pager` or any other
pager-like places which want to format git-patch output.
- .gitconfig:
- core.pager: use new `diff-pager` wrapper script.
- interactive.diffFilter: use new `diff-filter` wrapper script.
This lets `git add -i ...` use the same shared diff-filter.
- color.diff-highlight: Tweak colors so that "normal" colors have
a normal [non-colored] foreground color, and "highlight" colors
can be simply "red bold" and "green bold" respectively. This
eliminates visual clutter from the colored diff display, so that
the diff output is less noise [for line-pairs which
`diff-highlight` can process].
Tony Duckles [Sat, 6 Jan 2018 14:47:09 +0000 (08:47 -0600)]
.vimrc: Use autocmd for adding Solarized highlight overrides
Use 'autocmd ColorScheme solarized' to trigger adding the override
'highlight' rules to override default Solarized colorscheme
highlighting.
This ensures that these highlight rules get added when changing the
colorscheme [back] to 'solarized'. This also compartmentalizes these
overrides to the Solarized colorscheme.
Tony Duckles [Sat, 23 Dec 2017 15:23:10 +0000 (09:23 -0600)]
.vimrc: Cleanup 'highlight' overrides
The current colorscheme should set all the standard 'highlight'
groups. No need to override them locally.
- Remove all 'guifg'/'guibg' overrides, keep only terminal-type
overrides. GUI sessions (e.g. gvim) should use 24-bit colors
as defined in current `colorscheme`.
- Remove 'StatusLine' highlights. Everything status-line is handled
by `vim-airline`.
- Only define override 'SpecialKeys' highlights if we're using a
16-color $TERM [because I don't like the default solarized color-
scheme 'SpecialKeys' highlight colors].
- Remove 'Todo' highlight. The current `colorscheme` should define
this, no need to override it.
Tony Duckles [Sat, 16 Dec 2017 02:05:58 +0000 (20:05 -0600)]
.vim: Switch to use junegunn/vim-plug as plugin manager
Stop tracking vim plugins as discrete submodules. Instead use
junegunn/vim-plug to manage installing and updating plugins. This
allows maintaining the plugin list via my .vimrc file.
Tony Duckles [Sun, 22 Feb 2015 01:35:17 +0000 (19:35 -0600)]
.bash_profile: Don't run keychain when sudo'ing
Don't re-run keychain when starting a sudo'd shell. When using
Fabric + sudo, this was re-running keychain and borked the
pre-existing ssh-agent job. Use presence of $SUDO_USER to identify
sudo context and prevent re-running keychain.
Tony Duckles [Sat, 3 Jan 2015 23:46:46 +0000 (17:46 -0600)]
.bashrc: Don't include system bashrc, enable more shell options
* The system bashrc (/etc/bashrc) can bring in extra stuff we don't
want, e.g. on work machines. Don't source it anymore.
* Enable additional shell options
git.nynim.org / dotfiles.git / log