The deploy script was simply redirecting the contents of the files into
the target files, however, they were getting created without executable
permissions. Since this script is designed to deploy executables, it is
required to set the executable permissions.
This cannot be done in the deployment configuration file however,
because the script parses all the input files first before extracting
the relevant contents. Therefore, if we try to run chmod +x within the
file, it would fail because the file would not exist yet (or run deploy
twice).
This commit also cleans up the formatting when building the command line
so that each command is set up on it's own line.
The deploy script was simply redirecting the contents of the files into
the target files, however, they were getting created without executable
permissions. Since this script is designed to deploy executables, it is
required to set the executable permissions.
This cannot be done in the deployment configuration file however,
because the script parses all the input files first before extracting
the relevant contents. Therefore, if we try to run chmod +x within the
file, it would fail because the file would not exist yet (or run deploy
twice).
This commit also cleans up the formatting when building the command line
so that each command is set up on it's own line.
Deploy files are bash scripts with a couple of extra commands - namely
the repo, target and file commands. This allows a user to specify a
deployment file with a source repository, destination folder and
specific Git version to extract.
Deploy files are bash scripts with a couple of extra commands - namely
the repo, target and file commands. This allows a user to specify a
deployment file with a source repository, destination folder and
specific Git version to extract.
Vim's statusline is now handled by the vim-airline plugin. This commit
removes the statusline cruft from vimrc and adds a tiny airline-settings
plugin to configure airline.
Since there's already a syntax enable line, having syntax on is
redundant. Also, it allows plugins to override the default colors,
rather than using the default Solarized colors
When executing commands over SSH, such as SCP, the server (tput)
complains that there is no terminal defined. This fix sets the T_*
variables only if the TERM variable is not empty.
With Terminal.app, the background color was getting set to base02
instead of base03, therefore, I had to use base03 (brightblack) to
distinguish the tmux status bar from the rest of the screen. It would
be a problem with vim (not so much really, since I could figure out
where the tmux status bar was based on the vim status line).
However, since iTerm2 is a better terminal emulator, it correctly
displays the background color as base03, so in order to distinguish the
status bar, I changed the color to base02 (black) instead.
This eases usage with readline and avoids XOFFing your screen everytime
you hit C-s by accident. This change also modifies a couple of key
bindings, such as using C-s C-s to switch to the last window, and C-s
M-k to clear the scrollback history and C-s C-y to toggle pane sync
Can now specify vim plugin bundles as short forms. Eg.:
- tpope/vim-pathogen - goes to github.com/tpope/vim-pathogen.git
- vimwiki - goes to github.com/vim-scripts/vimwiki.git
- any other form is not modified and passed straight through
Can also specify the transport mechanism to use when installing bundles.
This has no impact when updating bundles, since these will use the
remote url specified in the git repo.
Can also specify not to update existing bundles with a command line
switch.
This allows me to specify the destination folder if the link name
doesn't need to be changed, i.e., if I want to install
vim/ftplugin/ruby.vim, I no longer need to specify the following line:
lnfile vim/ftplugin/ruby.vim ~/.vim/ftplugin/ruby
Instead, I can simply give the destination folder, just terminate it
with a slash character as follows:
lnfile vim/ftplugin/ruby.vim ~/.vim/ftplugin/
nirenjan