Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/fraidev/dotfiles

my dotfiles :D
https://github.com/fraidev/dotfiles

dotfiles git macos neovim ocaml vim zsh

Last synced: 7 days ago
JSON representation

my dotfiles :D

Awesome Lists containing this project

README 

        
# Dotfiles



This is a my dotfiles, I started with a [nicknise](https://github.com/nicknisi/dotfiles) repository fork. 



![capture-demo](https://user-images.githubusercontent.com/25258368/181651042-ea7520e3-deb1-4a0e-858e-0a17f6d2ba5f.png)



## Initial Setup and Installation



### Backup



First, you may want to backup any existing files that exist so this doesn't overwrite your work.



Run `install/backup.sh` to backup all symlinked files to a `~/dotfiles-backup` directory.



This will not delete any of these files, and the install scripts will not overwrite any existing. After the backup is complete, you can delete the files from your home directory to continue installation.



### Installation



If on OSX, you will need to install the XCode CLI tools before continuing. To do so, open a terminal and type



```bash

➜ xcode-select --install

```



Then, clone the dotfiles repository anywhere you like on your machine.



```bash

➜ git clone https://github.com/nicknisi/dotfiles.git

➜ cd dotfiles

➜ ./install.sh

```



`install.sh` will start by initializing the submodules used by this repository (if any). **Read through this file and comment out anything you don't want installed.** Then, it will install all symbolic links into your home directory. Every file with a `.symlink` extension will be symlinked to the home directory with a `.` in front of it. As an example, `vimrc.symlink` will be symlinked in the home directory as `~/.vimrc`. Then, this script will create a `~/.vim-tmp` directory in your home directory, as this is where vim is configured to place its temporary files. Additionally, all files in the `$DOTFILES/config` directory will be symlinked to the `~/.config/` directory for applications that follow the [XDG base directory specification](http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html), such as neovim.



Next, the install script will perform a check to see if it is running on an OSX machine. If so, it will install Homebrew if it is not currently installed and will install the homebrew packages listed in [`Brewfile`](Brewfile). Then, it will run [`osx.sh`](install/osx.sh) and change some OSX configurations. This file is pretty well documented and so it is advised that you __read through and comment out any changes you do not want__.



## Terminal Capabilities



In order to properly support italic fonts in and out of tmux, a couple of terminal capabilities need to be described. Run the following from the root of the project:



```bash

tic -x resources/xterm-256color-italic.terminfo

tic -x resources/tmux.terminfo

```



## ZSH Setup



ZSH is configured in the `zshrc.symlink` file, which will be symlinked to the home directory. The following occurs in this file:



* set the `EDITOR` to nvim

* Load any `~/.terminfo` setup

* Set the `CODE_DIR` variable, pointing to the location where the code projects exist for exclusive autocompletion with the `c` command

* Recursively search the `$DOTFILES/zsh` directory for files ending in .zsh and source them

* Setup zplug plugin manager for zsh plugins and installed them.

* source a `~/.localrc` if it exists so that additional configurations can be made that won't be kept track of in this dotfiles repo. This is good for things like API keys, etc.

* Add the `~/bin` and `$DOTFILES/bin` directories to the path

* And more...



### Prompt



The prompt is meant to be simple while still providing a lot of information to the user, particularly about the status of the git project, if the PWD is a git project. This prompt sets `precmd`, `PROMPT` and `RPROMPT`. The `precmd` shows the current working directory in it and the `RPROMPT` shows the git and suspended jobs info. The main symbol used on the actual prompt line is `❯`.



The prompt attempts to speed up certain information lookups by allowing for the prompt itself to be asynchronously rewritten as data comes in. This prevents the prompt from feeling sluggish when, for example, the user is in a large git repo and the git prompt commands take a considerable amount of time.



It does this by writing the actual text that will be displayed int he prompt to a temp file, which is then used to update the prompt information when a signal is trapped.



#### Git Prompt



The git info shown on the `RPROMPT` displays the current branch name, along with the following symbols.



-  `+` - New files were added

-  `!` - Existing files were modified

-  `?` - Untracked files exist that are not ignored

-  `»` - Current changes include file renaming

-  `✘` - An existing tracked file has been deleted

-  `$` - There are currently stashed files

-  `=` - There are unmerged files

-  `⇡` - Branch is ahead of the remote (indicating a push is needed)

-  `⇣` - Branch is behind the remote (indicating a pull is needed)

-  `⇕` - The branches have diverged (indicating history has changed and maybe a force-push is needed)

-  `✔` - The current working directory is clean



#### Jobs Prompt



The prompt will also display a `✱` character in the `RPROMPT` indicating that there is a suspended job that exists in the background. This is helpful in keeping track of putting vim in the background by pressing CTRL-Z.



#### Node Prompt



If a `package.json` file or a `node_modules` directory exists in the current working directory, display the node symbol, along with the current version of Node. This is useful information when switching between projects that depend on different versions of Node.



## Vim and Neovim Setup



[Neovim](https://neovim.io/) is a fork and drop-in replacement for vim. in most cases, you would not notice a difference between the two, other than Neovim allows plugins to run asynchronously so that they do not freeze the editor, which is the main reason I have switched over to it. Vim and Neovim both use Vimscript and most plugins will work in both (all of the plugins I use do work in both Vim and Neovim). For this reason, they share the same configuration files in this setup. Neovim uses the [XDG base directory specification](http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html) which means it won't look for a `.vimrc` in your home directory. Instead, its configuration looks like the following:



|                         | Vim        | Neovim                    |

|-------------------------|------------|---------------------------|

| Main Configuration File  | `~/.vimrc` | `~/.config/nvim/init.vim` |

| Configuration directory | `~/.vim`   | `~/.config/nvim`          |



### Installation



Vim is likely already installed on your system. If using a Mac, MacVim will be installed from Homebrew. Neovim will also be installed from Homebrew by default on a Mac. For other systems, you may need to install Neovim manually. See their [web site](https://neovim.io) for more information.



[`link.sh`](install/link.sh) will symlink the XDG configuration directory into your home directory and will then create symlinks for `.vimrc` and `.vim` over to the Neovim configuration so that Vim and Neovim will both be configured in the same way from the same files. The benefit of this configuration is that you only have to maintain a single vim configuration for both, so that if Neovim (which is still alpha software) has issues, you can very seamlessly transition back to vim with no big impact to your productivity.



Inside of [`.zshrc`](zsh/zshrc.symlink), the `EDITOR` shell variable is set to `nvim`, defaulting to Neovim for editor tasks, such as git commit messages. Additionally, I have aliased `vim` to `nvim` in [`aliases.zsh`](zsh/aliases.zsh) You can remove this if you would rather not alias the `vim` command to `nvim`.



vim and neovim should just work once the correct plugins are installed. To install the plugins, you will need to open Neovim in the following way:



```bash

➜ nvim +PlugInstall

```



## Fonts



I am currently using [Operator Mono](http://www.typography.com/fonts/operator/styles/operatormonoscreensmart) as my default font which is a paid font ($199 US) and does not include Powerline support. You do not need this font at all and there is nothing directly referencing it in the setup. For a great, free programming font, check out Mozilla's [Fira](http://mozilla.github.io/Fira/). In addition to this, I do have [nerd-fonts](https://github.com/ryanoasis/nerd-fonts) installed and configured to be used for non-ascii characters via iTerm2's profile settings. If you would prefer not to do this, then simply remove the `Plug 'ryanoasis/vim-devicons'` plugin from vim/nvim.



## Tmux Configuration



Tmux is a terminal multiplexor which lets you create windows and splits in the terminal that you can attach and detach from. I use it to keep multiple projects open in separate windows and to create an IDE-like environment to work in where I can have my code open in vim/neovim and a shell open to run tests/scripts. Tmux is configured in [~/.tmux.conf](tmux/tmux.conf.symlink), and in [~/tmux/base16.sh](tmux/base16.sh), which defines the colors used, the layout of the tmux bar, and what what will be displayed, including the time and date, open windows, tmux session name, computer name, and current iTunes song playing. If not running on macOS, this configuration should be removed.



## Docker Setup



A Dockerfile exists in the repository as a testing ground for linux support. To set up the image, make sure you have Docker installed and then run the following command.



```bash

docker build -t dotfiles --force-rm --build-arg PRIVATE_KEY="$(cat ~/.ssh/id_rsa)" --build-arg PUBLIC_KEY="$(cat ~/.ssh/id_rsa.pub)" .

```



This should create a `dotfiles` image which will set up the base environment with the dotfiles repo cloned. To run, execute the following command.



```bash

docker run -it --rm dotfiles

```



This will open a bash shell in the container which can then be used to manually test the dotfiles installation process with linux.