Config my stuff
$ git clone https://github.com/jjangsangy/Dotfiles.git
- Will auto symlink default files from into your home directory prepended with a
dot
.
# Specify configuration file with -c
$ ./link.sh -c vim/vim.conf
- Aliases and path configurations and not OS specific.
- General automated build and linker scripts.
- OS X and Debian Configurations
- Vundle or Plug for managing plugins. Plug is fast but requires
Vim +Ruby
. - YouCompleteMe autocompletion library.
First install vundle
or run the install install_vundle.sh
.
Link the vimrc
and vimrc.bundle
files to your home, or use the link_files.sh
tool using vim.conf
file.
# Will symlink all the vimrc and bundle
$ ./link_files.sh -f vim/vim.conf
Run BundleInstal
for Vundle or PlugInstall
to install vim packages.
You will need to have CMake and the ability to compile C++ to successfully install the compiled components of the
YouCompleteMe
package. There have also been issues when using different versions of Python that do reference the System Python.
- Executible scripts and programs
Programs and configurations for enviornments using the Bourne Again shell. Most files are POSIX compliant and should operate correctly in most cases, albeit some exceptions occur between compatability between BSD machines. Some of those exceptions below.
- Anacondas
.condarc
configuration files ipython notebook
configs and customcss/js
- MacOSX enviornments not having GNU Coreutils will need to install it with homebrew.
$ brew install coreutils
- Homebrew doesn't cloud BSD $PATH namespace by name mangling
binaries prepended with
g
- Files and directory highlighting requires coreutils
ls
anddircolors
. You can either rename binaries or create a new symbolic link like so
# Symbolically links `gls` to `ls`
$ ln -s "$(brew --prefix)/bin/gls" "$(brew --prefix)/bin/ls"
$ ln -s "$(brew --prefix)/bin/gdircolors" "$(brew --prefix)/bin/dircolors"
Ubuntu and Debian have different
.rc
naming conventions than OS X.Use
.bash_profile
or.bashrc
forlogin shells
instead of.profile